[MGNLPN-377] After upgrade publishing fails for nested component variants within page variants Created: 12/Apr/17 Updated: 08/May/17 Resolved: 02/May/17 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | 1.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Gange | 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
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
w/ publishing page variants, it seems if our page contains component variants the components do not come across to public. this is caused by |
| Comments |
| Comment by Richard Gange [ 12/Apr/17 ] |
|
The addition of the new node type mgnl:componentVariants seems to be causing the issue. |
| Comment by Julian Nodarse [ 19/Apr/17 ] |
|
To provide a little more detail, there is a work around for this issue by changing the itemType from mgnl:componentVariants to mgnl:variants . If this gets changed back however, then the issue from Ideal scenario is to be able to publish the default page, its page variants, and their variant components without having the default page overwrite the variant pages. The issue of the default page overwriting the variants is solved as per |