[MGNLSTK-1178] Start level of subnavigation not correct for sites with home not on top level Created: 05/Jun/13  Updated: 03/Feb/14  Resolved: 20/Jun/13

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: 2.0.10
Fix Version/s: 2.0.11, 2.5.1

Type: Bug Priority: Critical
Reporter: Will Scheidegger Assignee: Jaroslav Simak
Resolution: Fixed Votes: 1
Labels: navigation, stk
Remaining Estimate: 1h
Time Spent: Not Specified
Original Estimate: 1h

Attachments: PNG File Screen Shot 2013-06-05 at 10.14.43.png    
Issue Links:
Relates
relates to MGNLSTK-1300 Vertical Navigation isShowVerticalNav... Closed
relation
is related to MGNLSTK-949 Navigation: Start levels should be de... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

With MGNLSTK-949 one can now configure the start level of the sub navigation which is a very cool thing, BUT: If you do not configure a start level and you do not have your home page on the top level, the start level of the sub navigation is wrong.

Steps to reproduce:
1. go to demoauthor.magnolia-cms.com
2. create a new top level node of the type redirect
3. underneath create a second redirect node
4. copy the whole demo-project site underneath the second redirect node
5. open the copy of demo-project and navigate to some sup page
=> The sub navigation starts with "home" (i.e. 2 levels off)!

The problem lies on line 87 of SiteNavigationModel where the startLevel of the sub navigation is calculated by simply adding 1 to getHorizontalLevel() instead of adding the startLevel of the horizontal navigation (as it was done in 2.0.9).



 Comments   
Comment by Will Scheidegger [ 05/Jun/13 ]

Fix of MGNLSTK-949 caused this issue

Comment by Stefan Baur [ 12/Jun/13 ]

On Line 87, the startLevel property is overwritten instead of the addition that was in place earlier.

Generated at Mon Feb 12 07:34:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.