Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
None
Description
Steps to reproduce
- Create a page (master) to the root node (named livecopy-test)
- Create a livecopy sites of master and name it lc-de and lc-com
- Add some content to master (i.e. add component(s))
- push to lc-de site
- open lc-de and see that the content is correctly pushed
- open lc-com and see that the content is not there as expected (without this step all works fine)
- made some more changes on master - livecopy-test
- made push and publish to both lc-de and lc-com
Expected results
Content is pushed to lc-com and lc-de.
Actual results
Content is not pushed to lc-com. No error
Workaround
- render page before creating live copy (main/footer nodes would be created and referenced correctly)
Development notes
- open lc-com and see that the content is not there as expected
When this step is done, areas nodes are created empty in jcr:
When the content is pushed to this site (lc-com) the masterContentIdentifier cannot be found and a new node is created. In the logs this messages can be seen:
2021-02-08 19:11:26,569 WARN vecopy.actions.PropagateMasterContentChangesHelper: child page /lc-com/lc-test/main does not have the master content identifier 2021-02-08 19:11:26,569 WARN vecopy.actions.PropagateMasterContentChangesHelper: Cannot find the master node for /lc-com/lc-test/main. 2021-02-08 19:11:27,824 WARN vecopy.actions.PropagateMasterContentChangesHelper: child page /lc-com/lc-test/footer does not have the master content identifier 2021-02-08 19:11:27,824 WARN vecopy.actions.PropagateMasterContentChangesHelper: Cannot find the master node for /lc-com/lc-test/footer.
As a consequence a new node main0 and footer0 is created but the page try to render main and footer. This is the code in JCR:
Checklists
Acceptance criteria
