[MGNLSTK-670] Preview of versioned content results in freemarker exception Created: 27/Jul/10  Updated: 08/Mar/11  Resolved: 03/Nov/10

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: demoproject
Affects Version/s: 1.3.1
Fix Version/s: 1.3.6, 1.4

Type: Bug Priority: Critical
Reporter: Zdenek Skodik Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
causality
caused by MAGNOLIA-3360 versioning: children returned by Cont... Closed
relation
is related to MGNLSTK-658 main.ftl: template should react on pr... Closed
is related to MGNLSTK-604 Variations are not resolved properly ... Closed
is related to MGNLSTK-605 Dynamically linked or aggregated cont... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

for include def.htmlHeader.template [on line 8, column 4 in templating-kit/templates/main.ftl]. Find the attachment for full stacktrace.

Reproduce-able f.e. at demo-features/content-templates.



 Comments   
Comment by Philipp Bärfuss [ 29/Jul/10 ]

Increased the priority. Is this happing for most ot the STK pages? If so I consider it being a blocker.

Comment by Zdenek Skodik [ 29/Jul/10 ]

Not for most of the STK pages. I can run into the issue just when promos content node is in place.

Comment by Philipp Bärfuss [ 03/Nov/10 ]

That was a bit tricky. Due to MAGNOLIA-3360 the inheritance of content was broken and it tried to render a page as a paragraph which lead to this wired exception.

Comment by Stefan Baur [ 03/Feb/11 ]

Hi

I am experiencing this bug using

  • Magnolia EE 4.3.5
  • STK 1.3.4
  • ETK 1.3.2

Is it possible for me to just update the STK&ETK staying on version magnolia 4.3.5, or do I need to update to a newer magnolia version due to dependencies?

And if I can just update STK, what version should I use?

Comment by Zdenek Skodik [ 03/Feb/11 ]

Because of the dependency on core module, it's not enough to update just the STK module.
It might worth updating to 4.3.8, most likely the last release at 4.3 branch.
Or better don't hesitate to jump to the current 4.4.2 release.

Comment by Philipp Bärfuss [ 11/Feb/11 ]

Most of the version view related fixes were done in Magnolia 4.4 core classes which the STK depends upon.

Generated at Mon Feb 12 07:29:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.