What is this?
This Plone product gives you a new set of Ploneboard workflows. The idea is to update the basic workflows to use also new Plone 3 style roles.
Be aware. Yes, we overwrite the basic Ploneaboad workflows, so you don’t need to perform additional operation (just “Manage Security Setting” inside ZMI).
Also some basic Ploneboard security settings has been changed. Forum inside private folders are no more accessible. No more “Anonymous” explicit view permissions!
Roles
Keeping Member, Manager and Reviewer role settings, the new workflows set add special permissions also to Reader and Contributor roles.
Here a general explanation:
- Reader
A Reader can access forum and discussions normally. The only difference from a Reader and a normal user is inside private boards (or when boards are put inside private folders). A Reader can’t see not-published comments.
- Contributor
A Contributor can write inside a forum. Basic Ploneboard workflows manage only the Member or Owner role, so is not simple to make groups of users that can write inside forums and other not. In general, Contributors can write inside boards and forum not accessible to all members of the site.
TODO
Need tests!
Credits
Developed with the support of Azienda USL Ferrara; Azienda USL Ferrara supports the PloneGov initiative.
Authors
This product was developed by RedTurtle Technology team.
Changelog
0.1.4 (2013-02-11)
Reviewers now can delete and modify comments in all states [micecchi]
Editors can add new forums [micecchi]
Editors can modify ploneboard AT [micecchi]
Editors can remove conversations [micecchi]
0.1.3 (2012-05-08)
Fixed moderated workflow for anonymous. Now they can request review comments [micecchi]
0.1.2 (2012-05-03)
Fixed moderated workflow for anonymous. Now they can add comments [micecchi]
Added “Add Comment Attachment” permission to Anonymous for moderated and freeforall forums [micecchi]
0.1.1 (2010-07-01)
Removed GS profile dependency from Ploneboard. This make the product compatible with older versions of Ploneboard [keul]
0.1.0 (2010-06-14)
Initial release
Release files for Products.PloneboardModerationWorkflow 0.1.4
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 |
|---|---|---|---|---|
| Products.PloneboardModerationWorkflow-0.1.4.zip | 29.6 kB | Without provenance | Details for Products.PloneboardModerationWorkflow-0.1.4.zip |
Release files / Products.PloneboardModerationWorkflow-0.1.4.zip
| Download URL | Products.PloneboardModerationWorkflow-0.1.4.zip |
|---|---|
| Size | 29.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0ca29a8e9a596ee5a41c0dda2fd1bf94db0e2508adfcd42b6c6b42a4d61dbc8
|
|
BLAKE2b-256 checksum How to use checksums |
5e7fa451f8fd91bef97bc15ab090372fce754337d3b7c26e6e22d0b80f8efddc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.PloneboardModerationWorkflow 0.1.4
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.
