[MAGNOLIA-1030] hiding templates based on role acl does not work as described in wiki Created: 06/Sep/06 Updated: 20/Sep/06 Resolved: 20/Sep/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | security |
| Affects Version/s: | 3.0 RC2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Claudio Greuter | Assignee: | Boris Kraft |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
The following wiki Page describes a procedure how to restric access to template selection for editors: This example seems to be logical but does not work in magnolia RC3 the dropdown the templates contains an empty selection of double clicked unless i specify read only access to "/" (selected page and sub nodes) in the CONFIG ACL. however these rights are propagated down and all templates are then shown in the dropdown, even if i "deny" read on /modules/templating/templates/samples/ |
| Comments |
| Comment by Sameer Charles [ 20/Sep/06 ] |
|
It works as expected |