[LIVECOPY-161] Duplicated areas on slave Created: 11/Sep/19  Updated: 08/Jun/20  Resolved: 05/Jun/20

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

Type: Bug Priority: Critical
Reporter: Jürgen Ulrich 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
Date of First Response:
Epic Link: Ext DAMs maintenance & partnership support

 Description   

Hi Magnolia Team,

if an editor creates a page and directly creates a live copy of this page without open the page, no areas will be created for master and slave. This will cause an issue on pushing content from master to slave, because in the following scenario there will be duplicate areas on the slave page.

Steps to reproduce:

  • Create a new page in the master, without open it afterwards!
  • Create a live copy of this page
  • Open the page in the slave
  • Close the page
  • Open the page in the master
  • Close the page
  • Push the master page to the slave
  • Go to the JCR Browser and take a look to the slave. There will be duplicates of the areas (e.g. master and master0). One with and one without the master identifier.

Best regards
Jürgen



 Comments   
Comment by Jan Schulte [ 04/Jun/20 ]

Should the main area be created when the page is created? Absolutely, however this is a historical shortcomming of the pages app. To solve this problem (and a few others in non livecopy related issues) the pages app must be changed.

Should push master overwrite slave.main instead of creating slave.main0? I thinks this is really a follow up error. I think it would be better to tackle the root cause.

 

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