[MGNLDATA-79] Activation of node may lead to "activation failed" when switching users. Created: 15/Oct/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Bug Priority: Major
Reporter: Andreas Weder (MP) (Inactive) Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 4.1.1 with corresponding Data Module, Mac OS X 10.5.8, Java 1.5, Tomcat 5.5


Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When I activate a particular node in the Data Module as one user, then edit the node as different user and try to activate again, I get a JavaScript alert box telling me that the "user is not allowed to add,edit,delete" a node at that level on my public instance. When I deactivate that node with the same user, then activate again, everything works fine.

I have my editor role defined such that users have read/write access to /contacts in the data repository on node and subnode level.

How to reproduce (can't really try that with the demo version, since we only can login as "superuser"):

  • define a editor role and assign r/w rights on node and subnode level on /contacts in data repository
  • assign that editor role to user a and user b (I actually defined a group, assigned the role to that group, then the group to user a and b).
  • log in as user a (e.g. superuser), go to the data module, activate one content.
  • log in as user b, change something in the same node, then try to activate -> the JS alert box appears and activation has failed.
  • as user b, first de-activate the node, then activate it again -> no error and activation was successful


 Comments   
Comment by Rainer Blumenthal [ 07/Jul/10 ]

I have just found out the same problem... if you give READ / WRITE access to "/" for data then the activation works.

But in my case this is not possible - i do have to give READ ONLY on root level.

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:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.