[LIVECOPY-210] Shield Live Copy against wrong masterContentIdentifier references Created: 07/Jul/20  Updated: 27/Aug/20  Resolved: 26/Aug/20

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

Type: Improvement Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Julie Legendre
Resolution: Won't Fix Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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)
Documentation update required:
Yes
Date of First Response:
Epic Link: Ext DAMs maintenance & partnership support

 Description   

When a master Page has a wrong masterContentIdentifier attribute the live copies will inherit it and, consequently, wrong content or non content will be updated when the master page performs a push.

Steps to reproduce

  1. Go to Pages App and create a Master page
  2. Move to JCR and create a property node called masterContentIdentifier
  3. Set the value "Hello"
  4. Move back to Pages App and create a Live copy of the master page
  5. Back to JCR, the live copy page inherited the wrong masterContentIdentifier

Expected results
The Live Copy pages ignores the wrong masterContentIdentifier and uses the UUID from the Master page

Actual results
Wrong masterContentIdentifier is inherited, so no push of the Master pages takes effects on the live copies.

Workaround
N/A

Development notes
N/A
 


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