Form Settings
This page has not been fully translated to English yet. The headings below give an overview; for full details please refer to the Japanese version.
The Form Settings tab controls form-wide behavior: email notifications, confirmation screen, post-submit action, design, etc.
Email Settings
- Admin notification email — sent to the site owner when a submission arrives
- Auto-reply email — sent to the submitter (uses the value of the Email field)
- Merge tags —
{FieldName}to insert a single field,{all}to insert all submitted values
Confirmation Screen
Toggle the input → confirmation → completion flow on or off per form. Layout is fully customizable via HTML Template.
Post-Submit Action
Three options:
| Action | Use |
|---|---|
| Show message | Display a completion message (default) |
| Custom HTML | Display arbitrary HTML / shortcodes |
| Redirect | Redirect to a URL (thank-you page, etc.) |
Design Settings
- Design presets — Default / Simple 1 / Simple 2 / Normal
- Custom CSS files — Upload up to 10 CSS files per form
- Required mark — Customize the default
*character
Validation Settings
Per-field custom error messages, plus form-wide options like error display position and scroll behavior.
Spam Protection
See Spam Protection.
Pre-filling Field Values via URL Parameters
Prefill field initial values by adding query parameters to the form URL — no code required. Useful, for example, when an event page's "Apply" button links to an entry form and you want to carry over which event the visitor is applying for.
- Give the field a field name matching the URL parameter key (e.g.
post_title). - Set the field's default value to
{field_name}(e.g.{post_title}). - In the Form Settings tab, under URL Parameter Settings, check Allow initial values from URL parameters and save.
The field name, the name inside the braces, and the URL parameter key must all be the same string — the braces are a switch that only activates when they match the field's own name, not a reference to another parameter. Opening https://example.com/entryform/?post_title=Seminar%20A then prefills the post_title field with "Seminar A". Use a hidden field to keep the value in the submission/email without showing it on screen.
URL-passed values can be edited by the visitor, so don't use them for sensitive data. To pull a post title from a post ID instead (tamper-proof, stays in sync), use the fplant_field_initial_value_{name} filter — see PHP Hooks.
External Site Embedding
Export / Import
Export form settings as JSON for backup or staging-to-production migration. Import on creation.