cs.ploneformdemo
This product is a demo product to check how a z3c.form based form is rendered in a Plone site. This is useful when designing the site, to check all the special features that a form needs, such as required fields, error messages, etc.
Installation
Install cs.ploneformdemo by adding it to your buildout:
[buildout]
...
eggs =
cs.ploneformdemo
and then running bin/buildout
After installing the addon using the Plone Control Panel, you can go to these URLs to check the forms:
Full form: http://plonesite.com/test-form-view
Full form with fieldsets: http://plonesite.com/test-form-fieldsets-view
Contribute
Issue Tracker: https://github.com/collective/cs.ploneformdemo/issues
Source Code: https://github.com/collective/cs.ploneformdemo
Support
If you are having issues, please let us know. We have a mailing list located at: project@example.com
License
The project is licensed under the GPLv2.
Contributors
Mikel Larreategi, mlarreategi@codesyntax.com
Changelog
1.0 (2021-02-22)
Initial release. [erral]
Metadata
Release files for cs.ploneformdemo 1.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 |
|---|---|---|---|---|
| cs.ploneformdemo-1.0.tar.gz | 27.1 kB | Without provenance | Details for cs.ploneformdemo-1.0.tar.gz |
Release files / cs.ploneformdemo-1.0.tar.gz
| Download URL | cs.ploneformdemo-1.0.tar.gz |
|---|---|
| Size | 27.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cfc5df6b768aee20c073d27854f0563414a28f07f65136d2f8fa3d841b4e8eea
|
|
BLAKE2b-256 checksum How to use checksums |
015e68f2ecb9e5ead758044499888f2676baddbad2b3f97efceaf6530155ed35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.5
|
Security for cs.ploneformdemo 1.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.