[MGNLSTK-1451] Anything but areas not merged properly on template level for variations Created: 09/Dec/14 Updated: 02/Jul/18 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | base system, templates |
| Affects Version/s: | 2.8.5 |
| Fix Version/s: | 2.8.x |
| Type: | Bug | Priority: | Major |
| Reporter: | Natascha Desmarais | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | merging, navigation, variations | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
M5.3.5 |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
When you create a variation on a template level, all configuration inside the "navigation" node is ignored. Doing the same in the site definition works as expected. Also tested putting a navigation node inside the template definition (not the variation) and this configuration works as well, the only "broken" link is navigation inside a variation of a template. Areas work fine too. |
| Comments |
| Comment by Natascha Desmarais [ 09/Dec/14 ] |
|
Attachments got a bit messed up. Correct order is: tempdef_navigation + tempdef_working |
| Comment by Natascha Desmarais [ 11/Dec/14 ] |
|
Just ran into other issues with that again. Also not working:
So it seems that anything outside of the areas node is actually not merged properly (did not test the theme node on a template variation level yet) |
| Comment by Jan Haderka [ 02/Jul/18 ] |
|
STK have been deprecated in September 2017. As part of this project nearing end-of-life, we are not planning to fix any of the existing issues except for the critical security issues. For more details, please consult documentation. |