[MGNLSTK-796] Content inheritance should filter on node types Created: 19/Sep/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: base system
Affects Version/s: 1.4.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

If you have a page structure that happens to follow exactly the structure expected by inherited nodes, you run into ugly issues.
To reproduce with the stk demo:

  • create a page under demo-project/about called promos
  • view demo-project/about; there should be a FreeMarker error on the right side of the page, where the promos are supposed to be displayed.

The same can happen if

  • using jcr browser, remove demo-project/about/extras.
  • create a page under demo-project/about called extras, then a subpage to that called extras1.
  • view demo-project/about.

(less likely, of course...)



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

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 07:30:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.