Django CMS Forms
Source: https://github.com/sim1234/cms_forms/
Installation
- Install
django-cms-formspackage. - Add
cms_formstoINSTALLED_APPSdjango setting. - Add
path("forms/", include("cms_forms.urls"))to your main url config.
Configuration
Configure this package by setting these variables in your django settings.
All settings are optional. The default values can be imported from cms_forms.config_defaults.
CMS_FORMS_REGISTER_PLUGINS: bool - A flag indicating if the package should register to cms all plugins mentioned in the following lists.
CMS_FORM_PLUGINS: List[str] - List of dot delimited paths to form plugins.
CMS_FIELD_PLUGINS: List[str] - List of dot delimited paths to form field plugins.
CMS_WIDGET_PLUGINS: List[str] - List of dot delimited paths to field widget plugins.
CMS_CHOICE_OPTION_PLUGINS: List[str] - List of dot delimited paths to choice option plugins.
CMS_CHOICE_FIELD_PLUGINS: List[str] - List of dot delimited paths to choice field plugins.
CMS_BUTTON_PLUGINS: List[str] - List of dot delimited paths to button plugins.
Documentation
TODO
Contributing
Feel free to propose any change, as long as it tested and passes the repo checks.
Here is a simple guide to development installation of the project:
git clone https://github.com/sim1234/cms_forms.git && cd cms_forms
apt-get install python3.8 docker docker-compose # these are system requirements
python3.8 -m venv venv && source venv/bin/activate
export PYTHONPATH=$PYTHONPATH:$(pwd)/examples
export DJANGO_SETTINGS_MODULE=installation.settings
pip install -r requirements-test.txt
flake8 .
black --line-length 120 .
pytest --cov cms_forms tests
docker-compose down && docker volume prune -f && docker-compose up --build --abort-on-container-exit # run selenium tests
The project is automatically built on tag push and a new release is published.
Metadata
Release files for django-cms-forms 0.1.2
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 |
|---|---|---|---|---|
| django_cms_forms-0.1.2.tar.gz | 17.9 kB | Without provenance | Details for django_cms_forms-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_cms_forms-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for django_cms_forms-0.1.2-py3-none-any.whl |
Total release size: 42.5 kB
Release files / django_cms_forms-0.1.2.tar.gz
| Download URL | django_cms_forms-0.1.2.tar.gz |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aca2339b387fe8ff84b4494d53e28dc67862add4a4074b3f7d67ee293801d948
|
|
BLAKE2b-256 checksum How to use checksums |
c4b30349cdb836e72c0b48825219a9e28924aae5c39787e8d294748fd23d3824
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.2
|
Release files / django_cms_forms-0.1.2-py3-none-any.whl
| Download URL | django_cms_forms-0.1.2-py3-none-any.whl |
|---|---|
| Size | 24.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3ea99decfb76167a360f68b39f97dd4e079f60e6dc073da3997c72b6f5c16f1c
|
|
BLAKE2b-256 checksum How to use checksums |
f793f2b4bddfb934d26371bc308d156eef4003665a71f9208d45aa31d2503d45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.2
|
Security for django-cms-forms 0.1.2
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.