Introduction
collective.memberapproval provides a user interface for pas.plugins.memberapproval. Together these products form a member approval process, making it possible to approve or disapprove member registrations to your website.
Management views
collective.memberapproval providess the following management views:
@@usergroup-userprefs: collective.memberapproval overrides the standard user management view with one that extends the standard view with a filter to list only Approved, only Disapproved or All users.
@@user-approval: This view will allow you to view and change the status of a specific user. You access it with the parameter ‘userid’, ie http://localhost:8080/Plone/@@user-approval?userid=theusername
@@user-approve: This view will approve the specified user. It does not provide any HTML view, but is usable for services such as providing a direct link to approve users from a notification email. Example: http://localhost:8080/Plone/@@user-approve?userid=theusername
@@user-disapprove: This view will disapprove the specified user. It does not provide any HTML view, but is usable for services such as providing a direct link to disapprove users from a notification email. Example: http://localhost:8080/Plone/@@user-disapprove?userid=theusername
@@user-approved: This view will return True if the user specified is approved, or None otherwise. It does not provide any HTML view. Example: http://localhost:8080/Plone/@@user-approved?userid=theusername
collective.memberapproval Installation
Add collective.memberapproval to the list of eggs to install, e.g.:
[buildout] ... eggs = ... collective.memberapprovalRe-run buildout, e.g. with:
$ ./bin/buildout
Install the product into the Plone site from the Add-ons control panel.
Contributors
Radim Novotny, Author
Lennart Regebro
Change history
1.0 (2014-01-31)
Added support for Plone 4.3.
1.0rc2 (2012-06-27)
Added new registered.pt and registered_notify_template.pt templates that includes information that the registration needs to be approved before you can sign in.
1.0rc1 (2012-06-26)
There are now three states: Pending, Approved, Disapproved. You can this way show all pending users. You can only approve or disapprove users, you can not make them pending once they have been approved or disapproved.
Having an approval link in the tabs confused the users, so I removed it.
Added a “Disapprove & Delete” button at the request from users.
Changed @@user_approved to @@user_approved for consistency.
1.0b1 (2012-05-31)
Fixed the tests. [regebro]
1.0a1 (2012-05-29)
Initial release
Release files for collective.memberapproval 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 |
|---|---|---|---|---|
| collective.memberapproval-1.0.zip | 40.3 kB | Without provenance | Details for collective.memberapproval-1.0.zip |
Release files / collective.memberapproval-1.0.zip
| Download URL | collective.memberapproval-1.0.zip |
|---|---|
| Size | 40.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52fc5d555d55a1e6d39f919312691a18947c30ab73ec210583c2e5238f9013fe
|
|
BLAKE2b-256 checksum How to use checksums |
26e902145ba16681cd9860d2bf4faf929c0a1860fac1b4ae65ef480f7b6fc129
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.memberapproval 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.
