[MGNLPN-314] variants have a confusing editing experience when using inheritance Created: 11/Aug/16 Updated: 17/Dec/18 Resolved: 17/Dec/18 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | 1.2.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Not an issue | 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 |
To see the issue, look at the footer on this page: https://demo.magnolia-cms.com/.magnolia/admincentral#app:pages:detail;/travel/variants/variant-0:edit If we look at the page from public there is no issue: See https://demopublic.magnolia-cms.com/travel/variants/variant-0 So in the end we don't see the doubling presented to the client, but it's confusing for the editor. The documentation implies that the copied footer would "take precedence", one could assume, but it's not clear. |
| Comments |
| Comment by Richard Gange [ 11/Aug/16 ] |
|
A quick test reveals that deleting the footer node from the variant causes no footer to appear. So the documentation is correct. The footer on the variant is decoupled from the original node. This means that when you create a variant any changes that you make to the original must be propagated manually to the variant, if need be. Meaning the variant is essentially a snapshot of a node at a certain time. From that point on they different nodes. |
| Comment by Richard Gange [ 17/Dec/18 ] |
|
I do not see this issue in the latest versions (5.7/6.0) |