sreplaj/userforms

UserForms enables CMS users to create dynamic forms via a drag and drop interface and without getting involved in any PHP code

5.3.0 2018-11-07 14:45 UTC

Requires

• silverstripe/cms: ^4.0
• silverstripe/segment-field: ^2.0
• silverstripe/versioned: ^1.0
• symbiote/silverstripe-gridfieldextensions: ^3.1

Requires (Dev)

• phpunit/phpunit: ^5.7
• squizlabs/php_codesniffer: ^3.0

Suggests

• colymba/gridfield-bulk-editing-tools: Allows for bulk management of form submissions
• silverstripe/gridfieldqueuedexport: Export large submission as CSV through queued jobs in the background

BSD-3-Clause

• David Craig
• Damian Mooyman
• Will Rossiter
• Christopher Pitt
• Scott Hutchinson

• silverstripe
• userforms

README

UserForms enables CMS users to create dynamic forms via a drag and drop interface and without getting involved in any PHP code.

Requirements

See the "require" section of composer.json

Features

• Construct a form using all major form fields (text, email, dropdown, radio, checkbox..)
• Ability to extend userforms from other modules to provide extra fields.
• Ability to email multiple people the form submission
• View submitted submissions and export them to CSV
• Define custom error messages and validation settings
• Optionally display and hide fields using javascript based on users input
• Displays a confirmation message when navigating away from a partially completed form.

Installation

$ composer require silverstripe/userforms

You'll also need to run dev/build. You should see a new page type in the CMS 'User Defined Form'. This has a new 'Form' tab which has your form builder.

Documentation

• Index
• Installation instructions
• Troubleshooting
• User Documentation

Thanks

I would like to thank everyone who has contributed to the module, bugfixers, testers, clients who use the module and everyone that submits new features.

A big thanks goes out to Jan Düsedau for drawing the custom icon set for the form fields.

Versioning

This library follows Semver. According to Semver, you will be able to upgrade to any minor or patch version of this library without any breaking changes to the public API. Semver also requires that we clearly define the public API for this library.

All methods, with public visibility, are part of the public API. All other methods are not part of the public API. Where possible, we'll try to keep protected methods backwards-compatible in minor/patch versions, but if you're overriding methods then please test your work before upgrading.

Reporting Issues

Please create an issue for any bugs you've found, or features you're missing.