[MGNLDATA-24] functions should be hidden based on user's permissions Created: 06/Mar/08  Updated: 16/Sep/15  Resolved: 28/Jul/08

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Wolfgang Habicht Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

local as well as http://demoauthor.magnolia.info/


Attachments: Text File GenericDataAdminTreeConfig.java.patch     Text File TypeAdminTreeConfig.java.patch    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

access-rights are incorrect
It seems that a user can modify the data repository even without having the correct permissions. However changes will not succeed.
Too many options ('New Folder', 'New Item', 'Delete all', ...) are enabled.

reproducibility:
log in as administrator
create new role 'test' and configure as following:
Config: read only (selected and sub nodes) to /modules/adminInterface/config/menu/data
Data: read only (selected and sub nodes) to /example
URL: get & post to /*

create new user 'dummy':
set only role /test

log out, log in as dummy
select in the menu 'Example' (in the only section Data)
--> I get the options 'New Folder', 'New Item', 'Delete all', 'Activate all' and 'Deactivate all'
--> at least 'New Folder', 'New Item' and 'Delete all' should not be activated, since read-only is configured

Click on 'New Item' --> the edit Window opens
enter name and comment
click on 'Save' --> the window reloads, but does not close. Also the entry is not saved.



 Comments   
Comment by Philippe Marschall [ 28/Jul/08 ]

Fix attached

Comment by Philippe Marschall [ 28/Jul/08 ]

The types tree has the same problem. This attached as well.

Comment by Magnolia International [ 28/Jul/08 ]

thanks for the patches! just applied them on trunk, will be available with 1.2.1

Comment by Michael Mühlebach [ 16/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 05:10:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.