d0bf02d25f
* Fixes #526 (autocomplete attributes) adds ability for text fields to store additional html5 autocomplete attributes, attributes are per text field and populated from a dropdown list from the html5 specification. (Credit card and password autocomplete values omitted as should user defined forms be used to collect this information?) * Options moved to config moved array of auto complete values out to config option as recommended * Clarify function updated name, and added description to make more obvious what function is for normal users * added translation for field names along with some localisation for DE/EN/ES/FR/IT/PL/RU languages * formatting changes and argument removal formatted array as chopped list, and remove argument that wasn’t required. * ADHD kicking in consistency changes.
UserForms
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
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.