[MGNLSTK-949] Navigation: Start levels should be definable. Created: 14/May/12  Updated: 05/Jun/13  Resolved: 28/Mar/13

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: concept, templates
Affects Version/s: 2.0.2
Fix Version/s: 2.0.10, 2.5

Type: Improvement Priority: Neutral
Reporter: Christian Ringele Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLSTK-1178 Start level of subnavigation not corr... Closed
is related to MGNLSTK-1140 SiteNavigationModel used should be in... Closed
is related to DOCU-422 startLevel property for navigation Closed
Template:
Acceptance criteria:
Empty
Release notes required:
Yes
Date of First Response:

 Description   

In training, I get often confronted with a need of STK regarding the Navigation.
On many pages out there, the vertical navigation displays the same pages as the horizontal navigation.
For example when the horizontal provides a dropdown based Navigation, that the displayed drop down level is the same as the starting level of the vertical navigation.

The implementation within STK is, that you cant define a starting level of the vertical navigation. It will always start one level below what the horizontal navigation displays. (line 89 of SiteNavigationModel)
I think the start level of the vertical navigation should be definable.

When trying to solve this problem within the code just for a project, I encountered the problem that I cannot inject a different SiteNavigationModel without using for EVERY stk page template a different STKPageMOdel class, because the STKPAgeModel does a 'new' allocation of the SiteNavigationModel instead of getting it by Components.

Line 88 in STKPageModel

public SiteNavigationModel getNavigation() {
        return new SiteNavigationModel(getDefinition().getNavigation(), getSiteRoot(), content);
    }


 Comments   
Comment by Marvin Kerkhoff [ 14/May/12 ]

One Example: http://www.sage.de/karriere/warum_sage.asp

Comment by Christian Ringele [ 06/Jun/12 ]

At least the IOC part should be changed, thats one line of code using components instead of new allocation.

Comment by Jan Haderka [ 10/Apr/13 ]

Actually it's more documentation required then release notes ... as of this ticket it is possible to define start level by adding startLevel property to <site-definition>/templates/prototype/navigation/[vertical|horizontal].

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