Uploaded image for project: 'Extended Templating Kit (closed)'
  1. Extended Templating Kit (closed)
  2. MGNLETK-71

class property inheritance from template-prototype

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Neutral
    • None
    • 1.4.4
    • multisite
    • None
    • Enterprise with STK (1.4.6) /ETK Magnolia 4.4.6

    Description

      Custom Navigation class-value is not taken by default from default site prototype template definitions.

      Reproduce the problem:

      1. Create a Java class for a custom site navigation implementation
        public class TestSiteNavigation extends SiteNavigation {
          private Area test;
        
          public Area getQuickArea() {
            return test;
          }
        
          public void setTest(Area test) {
            this.test= test;
          }
        }
        
      2. Compile and deploy
      3. Configure template prototype set class for the navigation to the fully TestSiteNavigation
        • Configure the test-area as disabled
      4. In the the home-template override the navigation test to be enabled (no other value override for now).
      5. The navigation is of type SiteNavigation instead of the new test-class

      Only workaround for now, any template re-defining the navigation (any property) enabled areas must explicitly set the navigation beans class instead that it is taken from prototype.
      Wouldn't it be nice to have the class defaulted from the template prototype.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              meglur Marco Glur
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: