The FormPlugin embeds a submission form into any page using a form definition stored on the server.
Use this plugin to place a data-entry form on a page. The form is defined as a JSON file on the server by an administrator — the plugin renders it as a Bootstrap form with client-side validation and submits responses without a page reload. Submissions are stored on the server and viewable in the admin panel.
For the full JSON schema used to define a form — field types, prefill, section grouping, and proxy submission — see Form Definition Reference.
Note: This plugin requires the
formsadd-on to be enabled by your administrator before it will work. The named form definition must also exist before the page is visited.
[{Form id='your-form-id'}]
| Parameter | Type | Default | Description |
|---|---|---|---|
id | string | (required) | The form identifier. Must match the filename of a form definition in the forms data directory (without the .json extension). |
Embed a contact or reservation form on any page:
[{Form id='contact-us'}]
[{Form id='clubhouse-reservation'}]
Two forms on the same page:
[{Form id='maintenance-request'}]
[{Form id='event-proposal'}]
Note: The form only renders if the definition file exists on this site. The
idmust match a file under the forms data directory.
"prefill" on a field, logged-in users see that field pre-populated with data from their profile (name, email, phone, unit address). The value is editable. Anonymous users see the field empty."section" in the definition create labelled <fieldset> groups. They contribute no data to the submission."proxySubmission": true, an extra fieldset (For Another Occupant) appears so staff can submit on behalf of a resident.startTime and endTime fields, the server rejects submissions where the end time is not later than the start time.[{Form}] directives with different id values can appear on the same page.