This form designer does not try to offer every last configuration possibility of Django’s forms, just through the administration interface instead of directly in Python code. Instead, it strives to be a tool which everyone can use right away, without the need for long explanations.
It offers a small set of predefined input fields such as:
Text fields (One line and multi line widgets possible)
E-mail address fields
Checkboxes
Dropdowns
Radio Buttons
Multiple selection checkboxes
Hidden input fields
Every field can optionally be declared mandatory, default values and help texts are available too. That’s it.
By default, form data is sent by e-mail to a freely definable e-mail address and stored in the database (a CSV export of saved submissions is provided too). It is possible to add your own actions, but that’s not documented yet. These actions aren’t hardcoded – they can be freely defined for every form defined through this form designer.
Configuring the export
The CSV export of form submissions uses the Python’s CSV module, the Excel dialect and UTF-8 encoding by default. If your main target is Excel, you should probably add the following setting to work around Excel’s abysmal handling of CSV files encoded in anything but latin-1:
FORM_DESIGNER_EXPORT = {
'encoding': 'latin-1',
}
You may add additional keyword arguments here which will be used during the instantiation of csv.writer.
ReCaptcha
To enable [ReCaptcha](http://www.google.com/recaptcha) install [django-recaptcha](https://github.com/praekelt/django-recaptcha) and add captcha to your INSTALLED_APPS. This will automatically add a ReCaptcha field to the form designer. For everything else read through the django-recaptcha readme.
Override field types
Define FORM_DESIGNER_FIELD_TYPES in your settings file like:
FORM_DESIGNER_FIELD_TYPES = 'your_project.form_designer_config.FIELD_TYPES'
In your_project.form_designer_config.py something like:
from django import forms
from django.utils.translation import ugettext_lazy as _
FIELD_TYPES = [
('text', _('text'), forms.CharField),
('email', _('e-mail address'), forms.EmailField),
]
Visit these sites for more information
form_designer: https://github.com/matthiask/form_designer
Release files for form-designer 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| form_designer-0.3.0.tar.gz | 13.6 kB | Without provenance | Details for form_designer-0.3.0.tar.gz |
Release files / form_designer-0.3.0.tar.gz
| Download URL | form_designer-0.3.0.tar.gz |
|---|---|
| Size | 13.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a37d1028cda2e98d004fb5c7f9351956aae19b96cf0957e98cd7fad5d093e31
|
|
BLAKE2b-256 checksum How to use checksums |
c81a31019f9c3cbad289aa1e935a5cf30ecf7744572bf56c57d61fe6b20b9025
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for form-designer 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
