This package was created to test several assumptions and suggestions to add some mockup patterns to the ‘anonymous’ js/css delivery of pages in Plone 5.2 . Easyform is the defacto forms packages on Plone 5.2 when you use Python3, but some of its fields require widgets that are by default only bundled and delivered to logged in users.
See https://github.com/collective/collective.easyform/issues/203
Contributors
Fred van Dijk, Zest Software, info@zestsoftware.nl
Changelog
1.0.1 (2022-03-19)
Fix wrong python_requires in setup.py. [fredvd]
1.0 (2021-12-13)
Rebuild bundle with Plone 5.2.6: - plone.staticresources 1.4.4 - Mockup 3.2.7 [fredvd]
1.0a2 (2021-03-11)
Fix uninstall profile to remove our resource and bundle. [fredvd]
1.0a1 (2021-03-09)
Initial release. Adds inline validation and pickadage patterns in an extra bundle to anonymous visitors. This is necessary when you use easyform on public websites. The bundle also gets merged into default.js when you run in production. [fredvd]
Metadata
Release files for collective.anonymouseditpatterns 1.0.1
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 |
|---|---|---|---|---|
| collective.anonymouseditpatterns-1.0.1.tar.gz | 202.9 kB | Without provenance | Details for collective.anonymouseditpatterns-1.0.1.tar.gz |
Release files / collective.anonymouseditpatterns-1.0.1.tar.gz
| Download URL | collective.anonymouseditpatterns-1.0.1.tar.gz |
|---|---|
| Size | 202.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
85016f77c44550ec1b926ed29e61175e4d3498e50dd708c25e32b7577df26f2e
|
|
BLAKE2b-256 checksum How to use checksums |
0745ca76dc26b25ae7410233a6cfd40010d5fcb1efccc9f455c251753e6fab07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.8
|
Security for collective.anonymouseditpatterns 1.0.1
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.