[DOCU-411] Disable navigation from a variation defined on the level of a concrete template Created: 11/Jun/12 Updated: 03/Nov/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Samuel Schmitt | Assignee: | Ruth Stocks |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
When on a concrete template (like stkArticle) you add a variation (like smartphone) and you want to disable the navigation it does not work. But if you disabled the navigation from the site definition variation, then it works... so it really seems that the variations merge does not work properly with a concrete template. The site definition variation wins against the template variation. How to reproduce:
Now you can try to disable the horizontal and vertical navigation from the variation smartphone defined on the site defintion level. Then it will work, no more navigation !! So for me it's a bug because at the end the configuration defined on a concrete template must win against the others. //jsimak |
| Comments |
| Comment by Ruth Stocks [ 10/May/13 ] |
|
Documented at: |