FusionCMS is currently in an open beta state and under heavy active development.

Forms

Requirements

Visitor and user engagement is one of the most reliable ways to judge the performance of a website. FusionCMS includes the means to create and manage forms and their collected responses straight from the control panel.

Creating a Form

You'll first want to give your form a name and description. Description is not a required field, but could be useful for organization and filtering purposes in the Control Panel.

The handle field will mimic the name field until you manually update it. handle is used in generating the storage table used for collecting responses.

Privacy

Next, choose what set whether or not you want to collect users e-mail and/or IP address. Selecting Collect e-mail address will automatically include a field to your form for collecting emails.

Check Response receipts if you want the user to receive a copy of their form submission.

Spam

Configure methods of spam prevention. FusionCMS provides built-in functionality for both Google reCAPTCHA or a native Honeypot approach. Both can be enabled at the same time.

E-mail

Next, configure who receives notifications when a response is collected.

You can also provide a reply to e-mail address (optional; default from address will be used if left empty).

Confirmation

Direct where the user will go after their response has been collected.

  • Default confirmation page w/ custom message.
  • Custom URL (i.e. /thanks)

Templates

Customize templates used to render your form and confirmation page.

Fields

Unlike the Matrix, you will add any additional fields to your form from the Fields tab.

Rendering Forms

Creating a form does not automatically create a page for that form. Instead, forms needs to be rendered within your theme in order to appear.

You may utilize the @form Blade directive supplied by FusionCMS to render your forms within your theme:

@form('contact_us')

The first parameter is the handle of the form you'd like to render. You may supply a second parameter to override which Blade view file you'd like to render. By default, this will reference the forms.default Blade view file.

Have questions?

We're always happy to help with code or other questions you might have. Contact support or chat live with us on Discord.

Last edited on Monday, March 30, 2020 (1 year ago)