[MGNLMIGRATION-151] ftl-templates: Fix access to area property 'enabled' Created: 29/Oct/12  Updated: 23/Apr/13  Resolved: 12/Apr/13

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: 1.1.4
Fix Version/s: 1.2.3

Type: Improvement Priority: Neutral
Reporter: wolf bubenik Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-4970 Fix access to area property 'enabled' Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

The access to the 'enabled' property with the bean pattern does not work:

[#if  def.header.sectionHeader.enabled]

This check could be skipped in most cases but for some special cases we need it. Thus such code should be replaced by

[#if  def.areas.sectionHeader.isEnabled()]


 Comments   
Comment by Philipp Bärfuss [ 08/Nov/12 ]

We cannot distinguish between good and bad occurences of the check.

But .enabled should always work, doesn't it?

Comment by Robert Šiška [ 23/Nov/12 ]

@Philipp Strangely, it does not. Only .isEnabled() works.

freemarker.core.InvalidReferenceException: Expression def.areas.faqItems.enabled is undefined

full error+stacktrace: http://pastebin.com/px4anhcv

Comment by Robert Šiška [ 12/Apr/13 ]

Fixed with MAGNOLIA-4970

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