/@@localroles-controlpanel
- Info
requires Plone4
Add or Remove local roles for objects using csv. The format of the csv file should be:
path,user-/group-id,role
The data gets processed line by line. At the end, you’ll get a notification on the number of successfully processed lines as well as verbose error notifications for each unsuccessful line. Be patient! The duration of the process depends on the number of lines of your csv and may take up to several minutes.
Example csv:
/Plone/front-page,Reviewers,Editor /Plone/front-page,usera,Contributor /Plone/news,userb,Reviewer /Plone/news,userb,Editor
Change history
Changelog
0.2 (2012-03-07)
made compatible with Plone 4.1.x [hplocher]
0.1 (2010-08-02)
Initial release
Contributors
Hans-Peter Locher, Author Ramon Bartl
Download
Metadata
Release files for collective.localrolespanel 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 |
|---|---|---|---|---|
| collective.localrolespanel-0.2.zip | 526.8 kB | Without provenance | Details for collective.localrolespanel-0.2.zip |
Release files / collective.localrolespanel-0.2.zip
| Download URL | collective.localrolespanel-0.2.zip |
|---|---|
| Size | 526.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63de4e0ce65c3f88bf63b136b24a9a5edfd23f946a43ded59c43a47334379530
|
|
BLAKE2b-256 checksum How to use checksums |
fc50db1787053f0b446eae772b388d7eb5b2749da9f99e454df4cc1243d8433b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.localrolespanel 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.