[MAGNOLIA-3765] Naming a Page "promos" causes rendering errors Created: 22/Jul/11 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | freemarker, rendering |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Sean McMains | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| 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 |
|
Steps to reproduce: 1. Log in Expected behavior:
Actual behavior:
out != pageContext.getOut(). Out is JspWriterAdapter wrapping a info.magnolia.cms.util.LazyInitPrintWriter@668bbdab pageContext.getOut() is null The problematic instruction: ---------- ==> user-directive cms.links [on line 46, column 1 in templating-kit/templates/global/htmlHeader.ftl] in include def.htmlHeader.template [on line 8, column 4 in templating-kit/templates/main.ftl] ---------- Java backtrace for programmers: ---------- freemarker.template.TemplateModelException: out != pageContext.getOut(). Out is JspWriterAdapter wrapping a info.magnolia.cms.util.LazyInitPrintWriter@668bbdab pageContext.getOut() is null at freemarker.ext.jsp.TagTransformModel.getWriter(TagTransformModel.java:111) at freemarker.core.Environment.visit(Environment.java:286) at freemarker.core.UnifiedCall.accept(UnifiedCall.java:130) at freemarker.core.Environment.visit(Environment.java:210) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:210) at freemarker.core.Environment.include(Environment.java:1483) Interestingly, when one tries to use a page name of "extras", it automatically gets renamed to "extras0", presumably because there's already an extras content node at that level. Changing to "footer" causes a similar problem, though. |
| 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. |