Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-22601

Integrate KnpMenuBundle in the DemoBundle

    XMLWordPrintable

Details

    • Icon: Story Story
    • Resolution: Fixed
    • Icon: Critical Critical
    • 5.4.0-beta1
    • 5.3-dev, 5.3
    • DemoBundle
    • None
    • Castor Core S2, Castor Core S3, Castor Core S4, Castor Core S5, Castor Core S6
    • 4

    Description

      In the demo bundle, unlike in legacy ezdemo, the sub-menu is not appearing (see the 2nd level in the top menu of http://ezmarketingautomation.com/eng/Shopping).

      In order to stick to the Symfony2 standards, and avoid reinventing the wheel, this should be fixed by integrating knplabs/knp-menu-bundle, the dominating solution for menus in Symfony2 projects.

      Behaviour

      In ezdemo, the top menu was mostly based on:

      The feature is actually quite simple. Content types that should show up in menus are whitelisted in MenuContentSettings.TopIdentifierList (menu.ini):

      • First level items are whitelisted items below the root location
      • Second level items are whitelisted items below the current 2nd level location (if any).

      Implementation

      A standard KnpMenu builder should make this implementation quite easy. We might wanna use a service instead, but this may actually decrease accessibility of the code with no real improvement.

      Future

      This implementation will only be made for the DemoBundle at this stage. Based on the experience of this integration, a proper, generic implementation, tied to the Repository Domain model + application, will be designed and implemented, presumably for the next version.

      Attachments

        Activity

          People

            Unassigned Unassigned
            roland.benedetti-obsolete@ibexa.co Roland Benedetti
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2 days Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 2 days, 4 hours, 20 minutes
                1w 2d 4h 20m