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

New master content is not pushed to multiple live copies

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Urgent Urgent
    • None
    • None
    • 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.

       

      Edit:

      The issue seems to be related only to creating new components. Editing or removing already existing components work without complications.

      The steps to reproduce are the following:

      1. In the pages-app: Create the node structure /MASTER/HOME/About, where "About" is a simple page template with header and content
      2. Create the root note /tenants
      3. Make two live copies from the node /MASTER/HOME, renamed them tho HOME_FR and HOME_US
      4. Move the live copies from / (root) inside the /tenants/ node.
      5. Alter smth in /MASTER/HOME/About, e.g. added a header element
      6. Select /MASTER/HOME and use the Action "PUSH master changes incl. subnodes"; alternatively we tried selecting /MASTER/HOME/About and used the action "PUSH master changes"

        Acceptance criteria

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

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD