[MGNLETK-71] class property inheritance from template-prototype Created: 21/Feb/12  Updated: 18/Feb/16  Resolved: 18/Feb/16

Status: Closed
Project: Extended Templating Kit (closed)
Component/s: multisite
Affects Version/s: 1.4.4
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Marco Glur Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Enterprise with STK (1.4.6) /ETK Magnolia 4.4.6


Template:
Acceptance criteria:
Empty
Date of First Response:

 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.



 Comments   
Comment by Michael Mühlebach [ 18/Feb/16 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 01:48:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.