Ticket #9572 (closed PLIP: wontfix)
Optionally copy roles from parent when blocking inheritance
Reported by: | dukebody | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | Templates/CSS | Version: | |
Keywords: | Cc: |
Description
http://plone.org/products/plone/roadmap/231
When you check 'Inherit permissions from higher levels' you get another checkbox 'copy roles from higher levels' which causes the inherited roles to be copied locally upon save.
Proposed by
dannyb
Proposal type
User interface
State
being-discussed
Definitions
Motivation
One thing that one wants to do quite often is to remove a subset of roles in a folder to restrict a particular user or group in that folder. Unfortunately Plone doesn't allow you to take away individual roles. Plone 2.x's horrible interface at least allowed you to do one thing: you could easily copy (visually, by looking) roles that come from higher levels because you simple saw them both. And it allowed you to give local roles while that same role was also inherited. With Plone 3, the form became a lot simpler but now it doesn't allow you to do that. First, when inheritence is blocked, you don't see these assignments anymore from higher levels and second, if you haven't unchecked the checkbox yet, it won't allow you to assigen a local role if that role is already inherited (the checkbox is replaced with an image).
So, I'd like to be able to copy all the roles locally and then adjust them to your need.
Assumptions
Proposal
Add a checkbox next to the inherit checkbox that becomes visible when the inherit box becomes unchecked. When the user clicks save, the inherited roles are copied locally and inheritance is blocked.
Implementation
Deliverables
Risks
None I can see.
Progress log
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.