[MGNLDATA-87] Read only access to data repository for anonymous user. Created: 12/Nov/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.3.2, 1.4
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Danilo Ghirardelli Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Website and dms repositories have the read only access to "/" and subnodes granted by default to the "anonymous" role.
Is there any reason to not grant a the same right to the anonymous role by default for the data repository? Now (even on the public demo) there is no right to access data module for anonymous role.



 Comments   
Comment by Bert Leunis [ 17/Nov/09 ]

I totaly agree with Danilo here. When working with the datamodule during development you forget about it, and this is always one of the first reported bugs. "I entered data, but it does not show up in the website". And then it takes some time to figure out what the problem is. So it saves us time, and I can not see any reason why anonymous shouldn't get read only rights by default.

This bug probably belongs to the MAGNOLIA project and not the DATA project.

Comment by Danilo Ghirardelli [ 20/Oct/11 ]

Just as a workaround, you can always add to you own module version handler, a line like this (sorry for the formatting, wiki didn't help):

tasks.add(new AddPermissionTask("Add access to data repo.", "Adding read only access to data module repository.", UserManager.ANONYMOUS_USER, DataModule.getRepository(), "", Permission.READ, true));
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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