[MAGNOLIA-3228] template recursion <cms:includeTemplate contentNode="${null}"/> Created: 16/Jun/10 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | taglibs, templating |
| Affects Version/s: | 4.3.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Peter Flood | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | taglib | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
We have a situation where we pass a node directly to the cms:includeTemplate, the node passed is found through inheritance so null is passed in if the node isn't found. With magnolia 4.2 this wasn't a problem however when we upgraded to 4.3.2 null values appear to cause the template containing the tag to be returned by the tag, thus creating infinite recursion and a server crash. |
| 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. |