Introduction
This package adds the support of captchas on spam-prone forms on a given Plone instance. Currently this package extends the user registration form from the package plone.app.users with the support for captcha views following the format found in collective.captcha. A compatible package must be installed before the captcha will function.
Installation
This package requires and is for Plone 4 or later. Plone 3.x does not depend on plone.app.users for the user registration form. To add the support for captchas on the form for those versions of Plone are done using the ZMI using the TTW editor on the registration template and script files.
Installing with buildout
You can install pmr2.cpatcha using buildout by adding an entry for this package in both eggs and zcml sections.
Example:
[buildout]
...
[instance]
...
eggs =
...
pmr2.captcha
zcml =
...
pmr2.captcha
Once the site is rebuilt, start the instance and install this product using the Add-ons panel in Site Setup.
Changelog
0.2 - 2012-11-07
Have zcml depend on plone.browserlayer as this package uses it.
Correcting dependencies and updated tests to be more resilient.
0.1 - 2012-10-30
Initial release
Metadata
Release files for pmr2.captcha 0.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 |
|---|---|---|---|---|
| pmr2.captcha-0.2.tar.gz | 6.2 kB | Without provenance | Details for pmr2.captcha-0.2.tar.gz |
Release files / pmr2.captcha-0.2.tar.gz
| Download URL | pmr2.captcha-0.2.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa1057c4ad268b320c8c701473e6b027121b4a53fb0e6d525b240537972c7f76
|
|
BLAKE2b-256 checksum How to use checksums |
d8ee8301484f2ceb7fb180dfdbe26f143069aba5f70718d6e7877de1c7ccb325
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pmr2.captcha 0.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.