SPWForm is a mail form plugin for WordPress. You define each form in the admin screen, place the generated shortcode on a page, and manage the mail settings \u2014 all without writing PHP. If you have built forms with traditional WordPress mail-form plugins, the shortcode-based workflow will feel immediately familiar.<\/p>\n\n
Each form is managed as a private custom post type. You can build the form body with shortcodes for common fields, configure auto-reply and administrator notification emails, and choose whether to use a confirmation step before sending.<\/p>\n\n
SPWForm suits both newcomers and experienced developers:<\/p>\n\n
Either way, you can start from the bundled sample and adjust the fields, emails, and validation to fit your site.<\/p>\n\n
[SPWForm_scode key=\"FORM_ID\"]<\/code>.<\/li>\n- Field shortcodes for text, textarea, email, hidden, radio, checkbox, select, and file upload fields.<\/li>\n
- Confirmation and completion flow support.<\/li>\n
- Auto-reply email and administrator notification email settings.<\/li>\n
- Custom validation rules for required fields, email addresses, matching fields, numbers, text types, URLs, postal codes, and phone numbers.<\/li>\n
- File upload support with configurable allowed file extensions.<\/li>\n
- Bundled structural and state safeguards for every form, plus an optional standard design loaded only on pages that render an enabled form.<\/li>\n
- Per-form completion message.<\/li>\n
- Optional separate input, confirmation, and completion URLs.<\/li>\n
- Noindex output for confirmation and completion pages when Step URLs are used.<\/li>\n
- Localized default sample forms for Japanese and English sites.<\/li>\n<\/ul>\n\n
Supported field shortcodes<\/h4>\n\n\n[spwf_text]<\/code><\/li>\n[spwf_textarea]<\/code><\/li>\n[spwf_mail]<\/code><\/li>\n[spwf_hidden]<\/code><\/li>\n[spwf_radio]<\/code><\/li>\n[spwf_checkbox]<\/code><\/li>\n[spwf_select]<\/code><\/li>\n[spwf_file]<\/code><\/li>\n[spwf_back]<\/code><\/li>\n[spwf_submit]<\/code><\/li>\n[spwf_confirm]<\/code><\/li>\n[spwf_reset]<\/code><\/li>\n<\/ul>\n\nNotes<\/h4>\n\n
SPWForm sends mail through WordPress' wp_mail()<\/code> function. Actual delivery depends on your server and mail configuration. For reliable delivery, configure your site and sender domain correctly, including SPF, DKIM, and DMARC where appropriate.<\/p>\n\n\n\n- Upload the plugin files to the
\/wp-content\/plugins\/spw-form\/<\/code> directory, or install the plugin through the WordPress Plugins screen.<\/li>\n- Activate the plugin through the Plugins screen in WordPress.<\/li>\n
- Open the SPWForm menu in the WordPress admin.<\/li>\n
- Create or edit a form.<\/li>\n
- Copy the generated shortcode, such as
[SPWForm_scode key=\"123\"]<\/code>.<\/li>\n- Paste the shortcode into the page where you want to show the form.<\/li>\n<\/ol>\n\n
When the plugin is activated on a site with no existing SPWForm forms, it creates one localized sample form.<\/p>\n\n\n
\nHow do I display a form?<\/h3><\/dt>\nCreate a form in the SPWForm admin screen, then place the generated shortcode on a page:<\/p>\n\n
[SPWForm_scode key=\"123\"]\n<\/code><\/pre>\n\nReplace 123<\/code> with the form ID shown in the form edit screen.<\/p><\/dd>\nCan I use a confirmation screen before sending?<\/h3><\/dt>\nYes. Add the back, submit, and confirm button shortcodes to the form body:<\/p>\n\n
[spwf_back value=\"Back\"]\n[spwf_submit value=\"Submit\"]\n[spwf_confirm value=\"Confirm\"]\n<\/code><\/pre>\n\nUse tag=\"button\"<\/code> on Back, Submit, Confirm, or Reset to render a <button><\/code> element. Back, Submit, and Confirm remain submit controls; Reset remains a reset control. For presentation, use the class<\/code> attribute with CSS defined by your theme. User-supplied style<\/code> attributes are not rendered.<\/p>\n\nYou can also configure separate Step URLs for input, confirmation, and completion pages.<\/p><\/dd>\n
Which file types can be uploaded?<\/h3><\/dt>\nThe file field supports an allow<\/code> attribute. Supported extensions include:<\/p>\n\njpg jpeg png gif webp pdf txt csv zip doc docx xls xlsx\n<\/code><\/pre>\n\nIf allow<\/code> is omitted, image file types are allowed by default.<\/p><\/dd>\nDoes SPWForm include spam protection?<\/h3><\/dt>\nYes. The core plugin includes two spam defenses that work without any configuration:<\/p>\n\n
\n- A honeypot field that silently drops submissions made by automated bots.<\/li>\n
- Rate limiting that stops the same visitor from sending many messages in a short time (by default, up to 5 sends per 60 seconds).<\/li>\n<\/ul>\n\n
These are enabled automatically. For stronger protection against targeted spam, add a CAPTCHA (reCAPTCHA is available in the Pro add-on).<\/p>\n\n
Please note: because these defenses are enabled by default, visitors who submit many times in quick succession (for example, several people sharing one office\/network connection) may occasionally see a \"please wait and try again\" message. Developers can adjust the limits with the spwf\/rate_limit\/*<\/code> filters.<\/p><\/dd>\nSubmissions are rejected with a security error. What should I check?<\/h3><\/dt>\nIf the form page is served from a full-page cache (for example WP Super Cache, LiteSpeed Cache, or a CDN), the security token embedded in the cached page can expire after several hours, causing later submissions to be rejected. Exclude the form page from full-page caching so each visitor receives a fresh page.<\/p><\/dd>\n
How are uploaded files protected on nginx or other non-Apache servers?<\/h3><\/dt>\nUploaded files are stored under wp-content\/uploads\/spwform\/<\/code>. These files are never linked by a public URL: the core plugin uses them only as email attachments, and the Pro add-on serves stored attachments through an authenticated admin request. On Apache, a bundled .htaccess<\/code> file blocks directory listing and direct access to this folder.<\/p>\n\nServers that do not read .htaccess<\/code> (for example nginx) ignore this protection. On such servers, add an equivalent rule to your server configuration to deny direct web access to the folder. For nginx:<\/p>\n\nlocation ^~ \/wp-content\/uploads\/spwform\/ { deny all; }\n<\/code><\/pre>\n\nAdjust the path if your uploads directory is in a non-default location. Because these files are never linked publicly, denying direct access does not affect any feature. File names are random and the folder cannot be listed, so this is a defense-in-depth measure.<\/p><\/dd>\n
Can I place multiple SPWForm forms on one page?<\/h3><\/dt>\nNo. Placing more than one SPWForm form on the same page is not supported. Please use one form per page.<\/p><\/dd>\n
Where can I find documentation?<\/h3><\/dt>\nDocumentation is available in the plugin admin screen. A Japanese guide is also available at:<\/p>\n\n
https:\/\/studio.squareman.net\/guide\/spwform\/<\/p><\/dd>\n\n<\/dl>\n\n\n
0.2.8<\/h4>\n\n\n- Bundled the translation files and loaded the plugin text domain so the interface follows the site language. Official translate.wordpress.org language packs take precedence automatically once they are available.<\/li>\n<\/ul>\n\n
0.2.7.4<\/h4>\n\n\n- Resolved the legacy default-sample detection so an unmarked sample is looked up once and cached in a dedicated option instead of rescanning every form on each check. The one-time resolution reads forms in finite date-ordered batches and still selects the oldest form that exactly matches the default structure; the cache is rebuilt when forms are saved, deleted, or imported, or when the default payload changes. Routine checks no longer scale with the number of forms.<\/li>\n<\/ul>","raw_excerpt":"Create and manage mail forms with shortcodes, confirmation screens, validation rules, file uploads, and customizable notification emails.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/343674","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=343674"}],"author":[{"embeddable":true,"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/squareman"}],"wp:attachment":[{"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=343674"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=343674"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=343674"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=343674"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=343674"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ja.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=343674"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}