sc.contentrules.group
Overview
sc.contentrules.group is a content rules action that creates a new group in a Plone site when executed.
Use case
In a portal you have an area for Products. This area, /products will hold folders for each product available.
Everytime a new folder (product) is added in this area we want a new group of users to be created.
This group can be used to give local roles to its users in this context.
Requirements
Plone 3.3.x and above (http://plone.org/products/plone)
Installation
To enable this product,on a buildout based installation:
Edit your buildout.cfg and add sc.contentrules.group to the list of eggs to install
[buildout] ... eggs = sc.contentrules.group
After updating the configuration you need to run the ‘’bin/buildout’’, which will take care of updating your system.
Sponsoring
Development of this product was sponsored by:
Credits
Erico Andrei (erico at simplesconsultoria dot com dot br)
Changelog
0.5 (2011-09-15)
Spanish translation [hvelarde]
Initial release [erico_andrei]
1 maintainer
Metadata
1 maintainer
Release files for sc.contentrules.group 0.5
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 |
|---|---|---|---|---|
| sc.contentrules.group-0.5.tar.gz | 15.1 kB | Without provenance | Details for sc.contentrules.group-0.5.tar.gz |
Release files / sc.contentrules.group-0.5.tar.gz
| Download URL | sc.contentrules.group-0.5.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90f17a1d8490d8a8adc4e7c7f63662a0194b72dcecd7c1134f6234c8138ddcb3
|
|
BLAKE2b-256 checksum How to use checksums |
4f53601a1cb30df5f5b6d864f5a6b2b82499486fba6fa198a3d69e0ef86480d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sc.contentrules.group 0.5
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.
