Uploaded image for project: 'Magnolia Standard Templating Kit (closed)'
  1. Magnolia Standard Templating Kit (closed)
  2. MGNLSTK-949

Navigation: Start levels should be definable.

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Neutral
    • 2.0.10, 2.5
    • 2.0.2
    • concept, templates
    • None
    • Yes

    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);
          }
      

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                jsimak Jaroslav Simak
                cringele Christian Ringele
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: