[MGNLPN-657] Page Variant switcher not working Created: 15/Jun/22 Updated: 05/Oct/22 Resolved: 07/Jul/22 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | 2.1.3 |
| Fix Version/s: | 2.1.4, 3.0.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 1h | Time Spent: | 1h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Epic Link: | Support | ||||||||||||||||||||||||||||||||||||
| Sprint: | DevX 13 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||||||||
| Description |
|
Page variants cannot be edited at all. Switching the page variant in the edit page window does not switch the variant. See full description on support ticket: https://jira.magnolia-cms.com/browse/SUPPORT-14789
Developer notes: this is a regression (
|
| Comments |
| Comment by Johannes Kessler [ 05/Oct/22 ] |
|
Question: This problem is fixed in 2.1.4 of the Personalization-Module and this is bundeled and depending on 6.2.22. Is there a posibility that this could be fixed in 6.2.15 which uses 2.0.14? |