Uploaded image for project: 'Live Copy'
  1. Live Copy
  2. LIVECOPY-316

New master content is not pushed to multiple live copies

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • None
    • 3.2.8
    • None

      When pushing a new content element, e.g. a new page header, to multiple live copies, the new element appears in only one of the live copies.

      Our test page tree is the following:

       
      /MASTER/HOME/About
      /tenant/HOME_FR/About (HOME_FR is a livecopy of /MASTER/HOME)
      /tenant/HOME_US/About (HOME_US is a livecopy of /MASTER/HOME)
       
      A new header was added to the simple page /MASTER/HOME/About and pushed to both live copies, but only appears in HOME_FR/About.
       
      For the one live copy not receiving the pushed changes we see logged errors like
       

      2022-06-14 16:24:34,545 WARN  vecopy.actions.PropagateMasterContentChangesHelper: Got more than 1 candidate for node /MASTER/HOME/About -> [node /tenant/HOME_FR/About, node /tenant/HOME_US/About]. Using node /tenant/HOME_FR/About2022-06-14 16:24:34,545 INFO  vecopy.actions.PropagateMasterContentChangesHelper: Checking if childNodes for: /tenant/HOME_FR/About should be deleted
      2022-06-14 16:24:34,551 ERROR vecopy.actions.PropagateMasterContentChangesHelper: Unable to find referenced page for: /MASTER/HOME/About referenced site: /tenant
      2022-06-14 16:24:34,552 WARN  vecopy.actions.PropagateMasterContentChangesHelper: Got more than 1 candidate for node /MASTER/HOME/About -> [node /tenant/HOME_FR/About, node /tenant/HOME_US/About]. Using node /tenant/HOME_FR/About
      2022-06-14 16:24:34,552 WARN  vecopy.actions.PropagateMasterContentChangesHelper: child page /tenant/HOME_FR/About/content-area does not have the master content identifier
      2022-06-14 16:24:34,552 WARN  vecopy.actions.PropagateMasterContentChangesHelper: Cannot find the master node for /tenant/HOME_FR/About/content-area.

      The behavior is reproducible on our side and has been tried several times starting with an empty tree structure in the pages app. Please try to reproduce this or give us feedback in case we are using the live copy module in a wrong way.

      To us it is a blocker in the attemt to migrate one of our projects from 6.1 to 6.2 where we were using a incubator (demo) livecopy version.

      We have also created a ticket here: https://jira.magnolia-cms.com/browse/LIVECOPY-315

      BR

        Acceptance criteria

              Unassigned Unassigned
              r.gross Roman Groß
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD