[LIVECOPY-164] Rewire and Push has different save logic Created: 07/Nov/19  Updated: 01/Sep/20  Resolved: 01/Sep/20

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: 3.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Marvin Kerkhoff Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: maintenance
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
Documentation update required:
Yes
Date of First Response:
Epic Link: Ext DAMs maintenance & partnership support
Story Points: 3

 Description   

A customer had the following scenario. They have three pages Master, A, B. All pages are referenced. They have users who have only write access to Master and A. Main problem is that push and rewire work differently when it comes to ACLs

 

 

Push works in the following way:

If you push content magnolia is writing content into A but not into B. Which is logical. 

and rewrite does nothing, meaning, to update on A and B.

 

AC

  • Rewire content should be applied to A because the user has the right to it but
  • B shouldn't be changed because the user doesn't have rights for that

 



 Comments   
Comment by Laura Delnevo [ 11/Nov/19 ]

Good morning marvink2  thank you for flagging Live Copy issues and suggesting a few enhancements too! Whilst the team is happy to review existing tickets, could I please ask you to raise any new critical issues through the Support project? This way we can ensure a quicker response and validation of the issues that otherwise might take a little longer for us to pick up. Thank you, Laura 

Comment by Laura Delnevo [ 01/Sep/20 ]

The issue is fixed on the released 6.2 version. As 6.1 is in its grace period, we won't fix this issue on this version as its reaching end-of-life (only critical and security issues are tackled at the moment for 6.1)

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