Description
Shed Form is a WordPress contact form plugin specifically designed for Japanese websites. It features a 3-step submission flow (Input → Confirmation → Complete), a visual form builder, built-in spam protection, and full submission history management.
Key Features:
- 3-Step Submission Flow — Input → Confirmation → Complete, the standard expected by Japanese website visitors
- Visual Form Builder — Drag & drop field arrangement with 12 field types
- Spam Protection — Cloudflare Turnstile integration, NG phrase scoring with silent blocking, IP blocking, and rate limiting
- Submission History — View, search, manage status, export to CSV, and review blocked submissions
- Email Logging — Full log of sent emails with one-click resend for failed deliveries
- Multiple Layouts — Table, Stack, Inline, and DL layouts with responsive support
- Form Scheduling — Set start/end dates to automatically open and close forms
- Japanese Validation — Hiragana, Katakana, postal code, and Japanese phone number validation built in
Supported Field Types:
text, textarea, email, tel, number, select, radio, checkbox, consent, date, file, hidden
日本語の説明
Shed Form は、日本の Web サイトに特化した WordPress 用お問い合わせフォームプラグインです。
主な機能:
- 確認画面付き3ステップ送信(入力→確認→完了)
- ドラッグ&ドロップでフィールドを配置するフォームビルダー
- Cloudflare Turnstile 連携、NGフレーズスコアリング、IPブロック、レート制限によるスパム対策
- 送信履歴管理(検索・ステータス管理・CSV出力・ブロック済み確認)
- メール送信履歴と再送信機能
- 4種類のレイアウト(テーブル・スタック・インライン・DL型)
- フォーム有効期限設定
- ひらがな・カタカナ・郵便番号・日本の電話番号バリデーション
Third-Party Services
This plugin connects to external services in the following cases:
Cloudflare Turnstile
When Turnstile spam protection is enabled in the form settings, the plugin Shed Turnstile (which this plugin uses for Turnstile) sends verification requests to Cloudflare’s API during form submission. Shed Form itself does not contact Cloudflare.
- Service: Cloudflare Turnstile
- Privacy Policy: https://www.cloudflare.com/privacypolicy/
- Terms of Service: https://www.cloudflare.com/website-terms/
- Data sent: Turnstile token (generated client-side), site key, user IP address
- When: Only when Turnstile is enabled and a form is submitted
ZipCloud (Postal Code Lookup)
When a form includes a postal code field with auto-fill enabled, this plugin sends the entered postal code to the ZipCloud API to retrieve the corresponding address.
- Service: ZipCloud
- Privacy Policy: https://zipcloud.ibsnet.co.jp/
- Terms of Service: https://zipcloud.ibsnet.co.jp/
- Data sent: Postal code (zip code) entered by the user
- When: Each time a user enters a postal code in a field with auto-fill enabled
- Note: This is a free, publicly available Japanese postal code lookup service. No authentication or personal data is required.
NG Phrase Cloud Update
When the administrator manually clicks the “Update from Cloud” button in the plugin settings, this plugin fetches the latest spam phrase list from the WP Shed server.
- Service: WP Shed
- Privacy Policy: https://wpshed.jp/privacy/
- Terms of Service: https://wpshed.jp/legal/
- Data sent: None (one-way download only)
- When: Only when the administrator explicitly clicks the update button
Installation
- Upload the plugin folder to the
/wp-content/plugins/directory, or install directly through the WordPress plugin screen. - Activate the plugin through the ‘Plugins’ menu in WordPress.
- Go to Shed Form → Form List to create your first form.
- Copy the generated shortcode (e.g.
[shedform_form id="1"]) and paste it into any page or post. - (Recommended) For spam protection with Cloudflare Turnstile, install and activate the plugin Shed Turnstile and set its Site Key and Secret Key. Then turn Turnstile on for each form in the form editor.
FAQ
How many forms can I create?
There is no limit. You can create as many forms as you need.
Can I place multiple forms on the same page?
Yes. Use different shortcode IDs, e.g. [shedform_form id="1"] and [shedform_form id="2"].
How does the spam blocking work?
The plugin scores submission content against NG (blocked) phrases. When the score exceeds a threshold, the submission is silently blocked — the user sees the completion screen, but no email is sent to the administrator. Blocked submissions can be reviewed in the Submission History under the “Blocked” tab.
Does this plugin support Cloudflare Turnstile?
Yes, through the separate plugin Shed Turnstile. Create a Turnstile site in your Cloudflare dashboard, install and activate Shed Turnstile, and enter the Site Key and Secret Key in its settings (or define SHEDTURN_SITE_KEY and SHEDTURN_SECRET_KEY in wp-config.php). Then enable Turnstile per form in the form editor. Shed Form → Settings shows whether Shed Turnstile is active and its keys are set.
What happens if a form uses Turnstile but the keys are missing?
A form with Turnstile turned on refuses to send while the Shed Turnstile keys are missing, so a submission is never accepted without a check (the form setting “Refuse to send when the keys are missing”, on by default for new forms). Forms that already used Turnstile before version 1.13.2 keep accepting submissions and are listed in a warning in the admin screens; turn the setting on for them.
What happens when a form reaches its expiration date?
The form displays a custom message (HTML editable) and rejects all submissions, including direct POST requests.
Can I export submission data?
Yes. Go to Shed Form → Submission History and click the CSV export button.
The admin notification email is not arriving. What should I check?
- Check Shed Form → Email Log — is the email status “sent” or “failed”?
- If blocked, check the “Blocked” tab in Submission History.
- If “failed”, check the error message and consider installing an SMTP plugin (e.g. WP Mail SMTP).
- Check your spam/junk folder.
Is there a paid version?
Shed Form itself is completely free. Optional paid add-ons are available at wpshed.jp.
Screenshots
Changelog
1.15.0
- New: Retention period. Set a number of days per form (Form settings > Basic) and a number of days for the mail log (Shed Form > Settings). Older entries are deleted once a day, together with their fields, notes and stored attachments. The default is no limit, as before. A change takes effect after one hour, and the screen shows how many entries would be deleted.
- New: “Do not put the submitted content in notifications” (per form). The admin notification mail, Google Chat and LINE then carry only the form name, time, serial number and a link to the admin screen. The mail log keeps no content either. The auto-reply to the sender is not affected.
- New: When you delete a form that has submissions, you can also delete its submissions. The default is to keep them, as before.
- New: Hooks for add-ons (for example encryption): shedform_store_field_value, shedform_read_field_value, shedform_mail_log_args, shedform_session_data_store, shedform_session_data_read, shedform_session_ttl, shedform_keyword_condition, shedform_setting_keys, shedform_submissions_purged.
- Fix: The Turnstile “Position” setting now works. The widget can be placed right after the consent checkbox (all four layouts); before, the setting was saved but ignored and the widget always appeared before the submit button.
- Fix: The data of the confirm screen is now removed at once when the send limit is reached (it used to stay for up to an hour).
1.14.0
- New: A per-form setting “Save sent mail in the mail log” (on by default). Turn it off to keep names, addresses and message text out of the mail log.
- Fix: A mail resent from the mail log now keeps its original sender name and Reply-To, so replying goes to the person who filled in the form. The mail log stores them in two new columns (added automatically when you update). Logs made before this version have no stored values and are resent as before.
1.13.7
- Fix: Duplicating a form now copies its settings (messages, mail, spam, colours). Before, the copy started with the defaults.
- Fix: A text, textarea or email field sent as an array (a crafted request) no longer causes a fatal error. Other input checks were made stricter: regular-expression presets, full-width / half-width, Japanese phone types, date type, repeated checkbox values.
- Fix: Reserved or duplicate field keys are now refused when saving a field.
- Fix: Text typed into a field that looks like a placeholder (for example {email}) is no longer expanded a second time in the mail. A “<” or “>” in the sender name no longer stops the mail.
- Fix: A ZIP file renamed to .pdf is now inspected like a ZIP. A file attached to a field hidden by a condition is no longer accepted.
- Fix: A form whose expiry message is empty is now closed when it is outside the period. Titles over 200 characters are shortened on create.
- Fix: Admin: the “Delete all” confirmation now shows which forms are affected; the 7 error-message fields that were not saved now are; status “Blocked” can be chosen and is shown in CSV; CSV export no longer raises a PHP 8.4 notice; uninstall removes the transients.
1.13.6
- Fix: A required file field now stops the form when no file is attached. Before, the check was never reached, so a form with a required file field could be confirmed and sent with no attachment. The check follows the same rule as the other fields: the “required” setting of the field, or a “required” validation rule.
- Fix: When a file field has several inputs and the first one is empty, a file chosen in a later input is no longer ignored.
1.13.5
- Change: The warning about validation rules that Shed Form does not implement now tells apart the rule email_format on a field of type email. The field type already checks the email format, so that rule is not needed and can simply be deleted. It is shown as a note, not as a warning that asks you to fix something, and a form that has only such rules is not listed.
1.13.4
- Fix: A field whose type the form screen cannot draw (for example the types “url” or “password” that can arrive from a form imported from another plugin) used to show an empty row. If it was required, the form could not be sent. Such a field is now shown as a text field, and the form edit screen lists the fields concerned.
- New: Validation rules that Shed Form does not implement (email_format, tel_format, url_format, zip_format, numeric, alpha, alphanumeric, katakana, hiragana, written by older versions of the MW WP Form Importer) had no effect. The form edit screen and the Shed Form admin pages now list the fields that have them and show the rule to use instead.
1.13.3
- Fix: Updating from 1.13.1 or earlier stopped the site with a fatal error (“Class Shedform_Form_Manager not found”) on sites that have a form with Turnstile turned on. The update step now loads the classes it needs.
1.13.2
- Fix: Text typed into one-line and multi-line fields is now saved as typed. Before, text such as “p<0.05 … (age >= 65)” lost the part between “<” and “>” (it was treated as a tag), a lone “<” became “<“, and percent-encoded characters in a URL (for example %E9%8D%8B) were removed. Saved values are escaped when they are shown (screens and admin pages) and the emails are sent as plain text.
- Security: Emails (notifications, auto-replies, resends from the submission history and the spam-hold notice) are now sent as plain text only while the email is being sent, even if another plugin sets every email on the site to HTML.
- Security: Values typed by visitors are made harmless for Google Chat notifications (the “<URL|text>” link syntax cannot be used to show a fake link).
- Change: A form with Turnstile turned on now refuses to be sent while the Shed Turnstile keys are missing (new setting “Refuse to send when the keys are missing”, on by default for new forms). Forms that already used Turnstile before this update keep the old behavior (they still accept submissions) and are listed in a permanent warning in the admin screens, so nothing stops suddenly; turn the new setting on for them.
1.13.1
- Security: File uploads now always refuse executable, script, browser-rendered and macro-enabled formats (for example exe, bat, js, html, svg, docm, xlsm, asp, jsp, url), even if the form’s allowed-extensions setting lists them. A file whose name has such an extension in the middle (for example
invoice.bat.pdf) is refused too. PDF, images, Office documents without macros, ZIP and other common formats are not affected. - Security: ZIP files are now inspected before they are accepted. A ZIP is refused if it cannot be read, holds an executable, a script or another archive (a ZIP, RAR or 7z inside the ZIP), uses an unsafe path or a symbolic link, has too many files, contains a very large or suspiciously compressed file, or expands to an unreasonable size. If the server’s ZipArchive extension is missing, ZIP files are refused because they cannot be inspected.
- New: A file field now has a “password-protected ZIP” setting. It is on by default (same behavior as before); turn it off to refuse password-protected ZIP files, whose contents cannot be inspected.
- Security: The upload limits in a file field’s settings are kept within the range the form editor allows (1 to 50 MB, 1 to 10 files), and the structure of the uploaded data is validated.
- Security: The random part of stored upload file names is longer (16 characters instead of 4), so the locations of uploaded files are harder to guess. Existing files are not renamed.
- Security: The attachment download in the admin sends
X-Content-Type-Options: nosniffandCache-Control: private, no-store, and the file name in the response header is sanitized. - Fix: The
.htaccessin the upload folder no longer uses a PHP directive that causes a 500 error on servers running PHP-FPM. The directive is now applied only under mod_php. Direct access to the folder stays denied, and existing folders are updated automatically. - Fix: If a mail-settings filter returns a non-string value for a text setting, the original value is now kept instead of causing a type error.
- Fix: If any one of the attached files is refused, the whole submission is now sent back to the input screen, and the message names each refused file and the reason (not allowed type, too large, content does not match the extension, unsafe ZIP, too many files). Previously the refused files were dropped without notice and the form went on to the confirmation screen.
- Tweak: The file field settings now show which formats are always refused.
1.13.0
- New: The recipient (To) of the admin notification email accepts several addresses separated by commas. Only valid addresses are used and duplicates are removed. Previously, entering more than one made the email fail to send.
- New: URL parameters can pre-fill fields, restricted to an allow-list. In a field’s settings, set a parameter name and the values it may accept. Values that are not allowed are ignored.
- New: The form title can be edited and saved from the top of the form edit screen.
- New: A notice appears on the form edit screen when Cloudflare Turnstile is turned on for a form but is not actually protecting it (the Shed Turnstile plugin is inactive or its keys are not set).
- New: When the server’s
max_input_varslimit is reached, Shed Form now refuses the submission instead of silently dropping fields, and shows a single notice in the admin with an estimate of the form’s size. - New: Extension points (filters, actions and a JavaScript API) so that add-ons can change mail settings, button labels, the completion message and redirect, condition operators, field types and the admin tabs. Existing forms behave as before.
- Fix: A field whose key matches a WordPress public query variable (for example
name,sorpage) no longer makes the form submission return a 404 error.
1.12.6
- Fix: Conditional logic: when several conditions on the same trigger field point at the same field (the usual way to show a field for more than one value), that field stayed hidden whatever value was chosen. It is now shown when any of those values is selected. Conditions with a single value behave as before.
- Fix: Fields hidden by a condition are no longer saved as empty entries in the submission history.
1.12.5
- Security: Expiry message is now inserted with
textContentinstead ofinnerHTMLon the front end, closing a DOM XSS sink in the expired-form message. - Security: The
.htaccessprotecting the upload directory now uses an Apache 2.2/2.4-compatible directive (mod_authz_coredetection) instead of the Apache 2.4-onlyRequire all denied, and adds aphp_flag engine off/<FilesMatch>fallback. Existing upload directories are refreshed automatically on update.
1.12.4
- Security: Client IP detection no longer trusts the
X-Forwarded-Forheader unconditionally. The header is now only used when the request demonstrably passes through a proxy (REMOTE_ADDRis a private/reserved address), and the right-most value is taken instead of the left-most one. This affects the rate limiting, IP blocking and spam scoring features, which previously could be bypassed by sending a forged header. The same logic is now shared with Shed Turnstile. - Tweak: Declared compatibility with WordPress 7.1.
1.12.3
- Tweak: Raised the default spam hold threshold from 30 to 45 to reduce false positives on legitimate submissions.
1.12.2
- Fixed: Fields set to “initially hidden” were incorrectly shown or appeared grayed out on the front-end form. Initial visibility is now derived automatically from the trigger field’s condition rules (“show when” targets start hidden; “hide when” targets start visible). PHP no longer sets the
disabledattribute on inputs — the JavaScript handler manages bothdisplayanddisabledstate on page load, eliminating the conflict between server-rendered state and client-side evaluation. - Fixed: Fields placed in the same row (multiple columns) were not hidden on page load even when configured as “initially hidden”. The table, DL, and inline layouts now attach
data-shedform-fieldanddisplay:noneto each individual column wrapper when multiple fields share a row, allowing the JavaScript handler to control per-field visibility independently. - Fixed: Conditional fields were hidden again after navigating Input → Confirmation → Back. PHP now evaluates the trigger field’s current value (from the session) to determine the correct initial visibility, so fields that were visible before the confirmation screen remain visible when returning to the input step.
1.12.1
- Added: Field conditional visibility — configure show/hide rules on select, radio, and checkbox fields. When a visitor’s selection matches a rule, dependent fields appear or disappear in real time. Hidden fields are excluded from validation, confirmation, email, and database storage. The admin UI uses dropdowns and checkboxes for rule setup, requiring no knowledge of internal field keys or option values.
1.12.0
- Added: LINE notification support per form — configure a Messaging API channel access token and user ID, customize the message body with template variables, and use the test-send button to verify the setup before going live.
1.11.0
- Added: Security tab — Turnstile, spam scoring, rate limit, blocked phrases/IPs, domain block, and company block settings are now grouped in a dedicated “Security” tab.
- Added: Form duplication — duplicate a form with all its fields, rows, and settings from the form list. The copy is created as inactive to prevent accidental publishing.
- Added: Domain block — block or score-add submissions whose email domain matches a per-form blocklist.
- Added: Company name block — block or score-add submissions whose specified field value partially matches a per-form blocklist.
- Fixed: Expiry messages no longer render an empty wrapper div when the message text is blank.
1.10.3
- Added: Form status toggle (enable/disable) in the basic settings tab — disabled forms are hidden from the front end.
- Added: Form list now shows status badges — Active, Accepting (with expiry), Before Open, Closed, or Disabled — with start/end dates displayed for forms with expiry settings.
1.10.2
- Added: Google Chat notification support per form — configure a Webhook URL, choose whether to include spam-held submissions, and customize the message body with template variables. A test-send button is available to verify the webhook before going live.
1.10.1
- Fixed: Page now smoothly scrolls to the form after transitioning to the confirmation or completion screen.
1.10.0
- Added: Error Messages tab — 17 error strings (required, email, length, pattern, checkbox count, etc.) can now be customized per form; empty fields automatically fall back to plugin defaults.
- Added: Per-form color picker settings for label background, label text, border, and badge colors (admin settings tab).
- Added: Per-form custom CSS textarea with an inline CSS selector and CSS variable reference guide.
- Added: CSS custom properties for table layout — label cell background (–shedform-label-bg), label text color (–shedform-label-text), and row border (–shedform-border).
- Added: Separate CSS variable for consent field and scroll-box border (–shedform-consent-border), decoupled from –shedform-border.
- Fixed: Per-form color and custom CSS settings are now reflected in the field settings tab preview.
- Changed: Form wrapper now outputs a data-shedform-id attribute to scope per-form CSS custom properties without cross-form interference.
- Changed: Badge colors now use CSS custom properties (–shedform-required-bg, –shedform-required-text, –shedform-optional-bg, –shedform-optional-text) for theming.
1.9.0
- Added: Bulk delete all submissions button on the submission history list page (with confirmation dialog, optional per-form scope, and physical file cleanup).
1.8.1
- Fixed: TinyMCE editor content changes in the settings tab now correctly trigger the preview update (switched to AddEditor event binding to handle async initialization).
- Fixed: Unsaved-changes warning now correctly detects saves from all save buttons (mail, settings, layout).
- Changed: Default layout style changed from table to DL for new forms.
- Changed: Default form max-width changed from 800px to 100%.
- Changed: Layout save button tooltip added to clarify which settings it saves.
1.8.0
- Fixed: DL layout and table layout now display correctly on mobile — padding overflow caused right-edge clipping; resolved by adding box-sizing: border-box and display: block !important to mobile media query.
- Fixed: DL layout mobile right-edge clipping further resolved — added overflow:hidden and max-width:100% to row, row-inner, dt, and dd elements; added overflow-x:hidden to preview body.
- Fixed: Preview pane right-edge clipping caused by vertical scrollbar — scrollbar-gutter: stable now reserves scrollbar space permanently so iframe width does not change when scrollbar appears.
- Changed: AJAX connectivity test button and usage guide moved from per-form basic settings to the global Settings page.
1.7.23
- Added: AJAX connectivity test button on the form edit page to diagnose admin-ajax.php access issues.
1.7.22
- Fixed: Sender email address field and Reply-To fields now correctly preserve template variables (e.g. {domain}, {shedform_email}) when saving mail settings.
1.7.21
- Fixed: Hardcoded Japanese strings in JS file slot UI now use i18n via wp_localize_script.
- Fixed: Expiry message fallback now uses translatable string via shedformData.
- Fixed: NG phrases API URL can now be overridden via shedform_phrases_api_url filter.
1.7.20
- Fixed: File remove button now displays as a compact red circle instead of a stretched oval.
1.7.19
- Improved: File upload UI redesigned to per-slot style. Each file gets its own input with an individual remove button. An “Add file” button appears when under the limit, allowing files to be added or removed one at a time.
1.7.18
- Added: Serial number counter can now be reset or set to an arbitrary starting value from the form settings screen. The display now shows “next number to be issued” starting from 1.
1.7.17
- Fixed: Serial number cache is now invalidated after atomic DB update to prevent stale values and duplicate numbers.
- Fixed: Conditional logic for radio/checkbox fields now works for all options (not just the first).
- Fixed: Zipcode auto-fill and maxlength attributes now work with the new validation format.
- Fixed: Admin spam test panel escapes NG phrases to prevent XSS.
- Fixed: Required file fields are now validated server-side.
- Fixed: File upload rejection (wrong type/size) now shows an error instead of silently discarding the file.
- Fixed: Rate limit counter is now incremented only after successful session validation.
1.7.16
- Fixed: Email confirmation validation now uses case-insensitive comparison to prevent false mismatch errors when the confirm field is a text type.
- Fixed: Required validation is no longer bypassed when a text/email/number/select/date field key is absent from the POST request.
1.7.14
- Added: “スパム判定を無効にする” option in security settings to skip all spam scoring (useful for email-only registration forms).
1.7.13
- Fixed: Spam score “no Japanese” check now targets only text/textarea fields; email-only forms are no longer incorrectly flagged.
- Fixed: Repeat IP spam score is now skipped when rate limiting is disabled, preventing false spam detection during testing.
1.7.12
- Fixed: Email confirmation validation rule now saves correctly when a target field key is entered in the admin form editor.
1.7.11
- Fixed: Add row button and field save button in the admin form editor now prevent double-click duplicate submissions.
1.7.10
- Fixed: Spam score for repeated IP submissions now respects the rate limit count setting instead of a hardcoded threshold of 5.
- Added: Explanation of spam scoring logic displayed below the spam score settings.
- Fixed: Plugin Check warning for mail log clear query (phpcs:ignore annotation added).
1.7.9
- Fixed: Confirmation screen not displayed when the same form shortcode appears multiple times on a page.
1.7.8
- Fixed: Session error (“セッションが切れました”) no longer occurs when the same form shortcode appears multiple times on a page.
- Added: Clear all button on the mail log page to bulk-delete mail send history.
1.7.7
- Fixed: Turnstile token is no longer sent to Cloudflare twice when the same form shortcode appears multiple times on a page (prevented timeout-or-duplicate verification failure).
1.7.6
- Fixed: Corrected the Shed Turnstile settings page link (was pointing to an invalid page slug).
1.7.5
- Fixed: Stacked layout confirmation screen label width now spans the full column width.
1.7.4
- Confirmed compatibility with WordPress 7.0
1.7.3
- Fixed: Uploaded files and database records now deleted when a submission is deleted (prevents personal data from remaining on server).
- Fixed: Cron file cleanup now scans subdirectories recursively (year/month hierarchy).
- Fixed: Redundant wp_unslash() calls removed from mail settings save handler.
- Fixed: Console log prefix updated from [WSF] to [Shed Form].
1.7.2
- Fixed: Zipcode auto-fill, conditional fields, and consent scroll not working due to dataset attribute name mismatch (wsf → shedform prefix).
- Fixed: Turnstile verification failure now shows an error message instead of silently re-rendering the form.
- Fixed: Redundant wp_unslash() calls in settings save handler (title, html, text, error, blocked_ips keys).
- Fixed: Form deletion now also removes related row records.
- Fixed: error_log() calls are now gated by WP_DEBUG.
- Fixed: Cloud phrase “version” value is now sanitized before saving to wp_options.
- Fixed: Cloud phrases with invalid regex patterns are now filtered out before caching (ReDoS prevention).
- Fixed: License header notation unified to GPL-2.0-or-later.
1.7.1
- Fixed: NG phrase list not saving when phrases contained regex patterns (double wp_unslash corrupted JSON).
- Fixed: syncJson() not called when phrases array is empty (全クリア not persisting).
1.7.0
- Added: Shortcode copy button on the form edit page.
- Added: Per-form maximum width setting (form_max_width).
- Added: “協業” and “情報交換” to default NG phrase list.
- Changed: NG phrase type label updated from “完全一致” to “部分一致(含む)” to accurately reflect matching behavior.
1.6.23
- Fix: Removed specific add-on names from FAQ to reflect current availability.
1.6.22
- Fix: Corrected Privacy Policy URL for WP Shed NG Phrase service in Third-Party Services section.
1.6.21
- Code quality: Renamed JS global variable
wsfPreviewtoshedformPreviewto comply with WordPress.org prefix requirements. - Code quality: Renamed
wpshed_option keys for NG phrase cache toshedform_prefix (shedform_default_phrases_cache, shedform_phrases_cache_version, shedform_phrases_cache_updated). Migration runs automatically on update. - Code quality: Removed obsolete
wpshed_license_key/wpshed_license_cacheoption writes from migration function (no longer used after updater removal in v1.6.19). - Code quality: Wrapped hardcoded
同意するstrings with__()for i18n in 3 locations. - Code quality: Added phpcs:disable NonPrefixedVariableFound to page-settings.php and form-complete.php template files.
- Disclosure: Added Terms of Service URLs for ZipCloud and WP Shed NG Phrase API in Third-Party Services section.
1.6.20
- Code quality: Added phpcs:disable for NonPrefixedVariableFound in all template files (view templates included from callbacks — variables are scoped to each template, not global API).
- Code quality: Added PluginCheck.Security.DirectDB.UnescapedDBParameter phpcs:ignore to RENAME TABLE migration query ($old_table/$new_table are built from $wpdb->prefix + hardcoded map, no user input).
1.6.19
- Changed: Removed custom auto-updater (WPShed_Updater) — plugin is distributed exclusively via WordPress.org.
1.6.18
- Fixed: Undefined method Shedform_Field_Manager::get_fields() in ajax_restore_submission() — changed to get_by_form() (caused fatal error on “process as normal” action).
- Code quality: Wrap consent confirmation label with esc_html__() for i18n.
- Code quality: Wrap CSV export status labels with __() for i18n.
- Code quality: Add esc_attr() to nav-tab-active and display:none inline style echoes in form editor.
1.6.17
- Security: Added nonce verification to mail log detail view (auto-read-mark access now CSRF-protected).
- Security: “詳細” list links in mail logs now use wp_nonce_url() to include nonce parameter.
- Security: Cross-link from mail log detail to submission detail now includes nonce for check_admin_referer() on the submissions page.
1.6.16
- Security: Added nonce verification to submission detail view (auto-read-mark state change now CSRF-protected).
- Security: Sanitize validation and extras JSON field values on save (rule → sanitize_key, message/param → sanitize_text_field, _url keys → esc_url_raw, regex param validated by shedform_validate_regex_phrase).
1.6.15
- Changed: All function, class, constant, hook, option, and table prefixes renamed from wsf_/WSF_ to shedform_/SHEDFORM_/Shedform_ to meet WordPress.org 4-character prefix requirement.
- Migration: Existing wp_wsf_* database tables automatically renamed to wp_shedform_* on upgrade (data preserved).
- Migration: Existing wsf_* WordPress options automatically migrated to shedform_* on upgrade.
1.6.14
- Changed: Credit display changed to opt-in (default OFF) — removes Trialware violation. Setting added to Shed Form → Settings.
- Changed: Upload directory moved from wp-content/shedform-uploads/ to wp-content/uploads/shed-form/ (wp_upload_dir() based). Automatic migration for existing users.
- Fixed: Inline
- Security: options JSON now sanitized recursively with sanitize_text_field(). validation/extras validated by json_decode() + key whitelist (regex patterns preserved).
- Disclosure: Added ZipCloud postal code API to Third-Party Services in readme.txt
- Updated: SortableJS 1.15.6 → 1.15.7
- Fixed: file_put_contents() replaced with WP_Filesystem API for .htaccess and index.php creation
1.6.13
- Code quality: Added phpcs:ignore for DirectQuery/NoCaching/SchemaChange/UnescapedDBParameter on migration ALTER TABLE and INFORMATION_SCHEMA queries in shed-form.php
- Code quality: Added Squiz.PHP.DiscouragedFunctions.Discouraged to ini_set phpcs:ignore in class-shedform-validator.php (restore-after-finally blocks)
- Code quality: Added NoCaching to $wpdb->update() phpcs:ignore in class-shedform-admin.php
- Code quality: Added UnescapedDBParameter to CSV export batch-query phpcs:ignore lines in class-shedform-admin.php
- Code quality: Added UnfinishedPrepare to $wpdb->prepare() with spread-operator placeholder in class-shedform-admin.php
- Code quality: Added InputNotSanitized to phpcs:disable block in sanitize_input_for_display() in class-shedform-form.php
- Code quality: Added NonceVerification.Recommended phpcs:ignore to read-only list filter GET params in page-submissions.php
- Code quality: Added InterpolatedNotPrepared and moved ReplacementsWrongNumber phpcs:ignore to correct lines in page-submissions.php
1.6.12
- Code quality: Added phpcs:ignore/disable annotations for PluginCheck.Security.DirectDB.UnescapedDBParameter across all DB-heavy files — table names from $wpdb->prefix are safe
- Code quality: Added phpcs:disable blocks to manager/template classes (field-manager, form-manager, row-manager, settings) for repetitive DirectQuery/NoCaching/InterpolatedNotPrepared false positives
- Code quality: Added phpcs:disable/enable blocks to sanitize_input() / sanitize_input_for_display() for NonceVerification.Missing — nonce verified by calling functions
- Code quality: Fixed remaining ini_set (restore in finally blocks) and set_error_handler phpcs:ignore annotations in shed-form.php and class-shedform-validator.php
1.6.11
- Code quality: Removed deprecated load_plugin_textdomain() call (auto-loaded since WordPress 6.7)
- Code quality: Added missing wp_unslash() to $_GET accesses in admin pages and mail-logs template
- Code quality: Added sanitize_url() to HTTP_REFERER handling in template helpers
- Code quality: Added phpcs:ignore annotations for justified WPCS false positives (DirectQuery on custom tables, NonceVerification on read-only admin GET params, ini_set/set_error_handler for ReDoS protection)
1.6.10
- Version bump for mobile performance investigation testing
1.6.9
- Added: Field description — each field can now have supplementary helper text displayed below the input
1.6.8
- Code quality: Removed wp_kses_post() from JSON fields (options/validation/extras) in ajax_save_field() — prevents silent corruption of regex patterns containing angle brackets
- Code quality: Nonce sanitization changed from sanitize_key() to sanitize_text_field() (WPCS compliance)
- Code quality: Replaced raw $_GET[‘status’] access with already-sanitized $filter_status variable in submissions page
1.6.7
- Security: Session token now stores form_id — token from form A can no longer be used to complete form B
- Security: Session token destroyed immediately after retrieval (was destroyed after DB write) — eliminates 1-hour replay window
- Security: Textarea fields capped at 20,000 characters server-side to prevent spam-scoring DoS via oversized input
- Security: Blocked phrase matching now runs per-field in addition to concatenated text, reducing split-phrase bypass risk
- Security: File uploads now reject filenames containing PHP/script extensions in any position (e.g., shell.php.jpg)
- Added: Honeypot hidden field — bots that fill the invisible field are silently blocked regardless of spam score
1.6.6
- Security: From: display name now encoded with RFC 2047 MIME encoding (mb_encode_mimeheader) — prevents header injection via non-ASCII characters or special chars
- Security: admin_email_to validated with is_email() and CRLF-stripped before passing to wp_mail()
- Security: Resend mail CC/BCC now re-validated with is_email() and CRLF-stripped on restore from DB
- Security: ajax_download_file() path check now uses trailing DIRECTORY_SEPARATOR (same pattern as set_attachments()) to prevent sibling-directory bypass
- Security: Email subject CRLF stripped at plugin layer in both admin notification and auto-reply
- Performance/Security: CSV export now streams in batches of 500 rows — prevents memory exhaustion on large datasets; keyword filter moved to SQL layer
1.6.5
- Security: CSV injection fix — user-supplied field values starting with =, +, -, @ are prefixed with a single-quote in CSV export
- Security: {page_url} tag now uses home_url() instead of $_SERVER[‘HTTP_HOST’] to prevent host-header injection
- Security: ReDoS validation probe improved with near-miss test strings; PCRE control verbs (*LIMIT_BACKTRACK etc.) now rejected at save time
- Security: pcre.recursion_limit added alongside backtrack_limit in all regex guards; try/finally ensures limit is always restored
- Security: field validation ‘pattern’ rule now runs with the same ReDoS guard as blocked-phrase regex matching
- Security: set_attachments() path check uses trailing DIRECTORY_SEPARATOR to prevent shedform-uploads-evil prefix bypass
- Security: wp_unslash() added to remaining $_POST accesses in admin handlers
- Added: Admin notice warning when server is Nginx (where .htaccess upload protection is ineffective)
1.6.4
- Security: ReDoS protection — NG phrase regex patterns now validated with length limit (500 chars) and pcre.backtrack_limit guard; malformed/explosive patterns are skipped with error_log
- Security: X-Forwarded-For IP spoofing mitigation — rightmost IP used instead of leftmost when behind a proxy
- Security: Email attachment path traversal prevention — set_attachments() now validates all paths with realpath() against the shedform-uploads base directory
1.6.3
- Security: Upload subdirectories (form_id/year/month) now get .htaccess and index.php protection on creation
- Security: Content-Disposition header uses RFC 5987 (filename*=UTF-8) for correct Japanese filename handling
- Fixed: ALTER TABLE migration queries annotated with phpcs:ignore (no user input, WPCS compliance)
1.6.2
- Security: XSS fix — …






