[LIVECOPY-316] New master content is not pushed to multiple live copies Created: 20/Jun/22 Updated: 20/Jun/22 Resolved: 20/Jun/22 |
|
| Status: | Closed |
| Project: | Live Copy |
| Component/s: | None |
| Affects Version/s: | 3.2.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Roman Groß | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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
|
||||||||
| Description |
|
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:
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 |