[MAGNOLIA-164] visibility of templates per role Created: 31/Oct/04  Updated: 17/Mar/09  Resolved: 25/Apr/05

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 2.0 Final
Fix Version/s: 2.1 Final

Type: New Feature Priority: Minor
Reporter: Uwe Rosebrock Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

n/a


Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

I would suggest that either roles or users also define the templates accessible -> if a new page is created only the assigned templates are available.



 Comments   
Comment by Sameer Charles [ 17/Nov/04 ]

only a GUI ACL?
we can implement it quickly but if someone uses API it wont respect these ACL
so it must be supported by core

Comment by Philipp Bracher [ 19/Apr/05 ]

Uwe posted his solution to the dev-list

we will adapt the following:

  • storing ACL and not the additional information in the role node
  • Update the cashed information in the Templat class or adding a getGrantedTemplates(request) method
Comment by Philipp Bracher [ 25/Apr/05 ]
  • It is possible to select the repository in the ACL-Tab of the role (web, users, roles, config)
  • You can pass also permissions to the templates
  • The dropdown of the tree uses AccessManager
Generated at Mon Feb 12 03:14:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.