
Feature request - Add setting to determine permission flow for 'global' sidebar
Reported by dleffler | December 19th, 2011 @ 06:32 PM | in 2.0.3 (closed)
In previous (pre-2.0.3) versions, the 'global' sidebar inherited permissions from the current page. In 2.0.3 (develop) it never inherits permissions from the page, so only the admin user has access to the 'global' sidebar and must grant permissions from that container to other users.
- We could add a security setting which has the algorithm continue to drop into the page permission check and act like the old permission system.
Comments and changes to this ticket
-
dleffler December 19th, 2011 @ 08:22 PM
- Assigned user set to dleffler
There is a broad assumption made with this feature and revising it may alleviate the issue.
-
dleffler December 20th, 2011 @ 06:08 AM
Might consider NOT implementing this since it appears we have a solution which will discretely determine 'global' scope modules (without an assumption based kludge) and can guarantee that all sectional modules/containers would inherit page permissions.
-
expNinja December 20th, 2011 @ 12:54 PM
- State changed from new to resolved
(from [e632ce739c08109e13ed658fc1761423a4ec79f8]) Changes to a correct algorithm (vs a kludge) for determining 'global' (non-sectional) modules to prevent their inheritance of page permissions. Also corrects create=edit permission logic. [#422 #215 #447 state:resolved owner:dleffler] https://github.com/exponentcms/exponent-cms/commit/e632ce739c08109e...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
Tags
Referenced by
-
215 Feature request - Restrict editing of "global" sidebar modules (from [e632ce739c08109e13ed658fc1761423a4ec79f8]) Changes...
-
422 Bug: 'create' permission should imply 'edit' permission also (from [e632ce739c08109e13ed658fc1761423a4ec79f8]) Changes...