Disabling ExtrasArea without need to define class property: BodyClassResolver
should first check if enabled, then cast.
-----------------------------------------------------------------------------------------------------------------------
Key: MGNLSTK-951
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-951
Project: Magnolia Standard Templating Kit
Issue Type: Improvement
Components: base system, themepop
Affects Versions: 2.0.2, 2.0.1, 2.0
Reporter: Christian Ringele
Assignee: Christian Ringele
Priority: Major
Fix For: 2.0.3
Disabling the extras area is the most common use case on templates, besides
reconfigure it.
When disabling the extras area by adding the property enabled=false, a class
cast exception happens in the BodyClassResolver.
Without the definition of the specific bean by the class property, the code
does not work.
But it is really really hard for people to find out why they get the freemarker
error without the class property, and then to find out what class to use.
The new code uses first a default AreaDefintion for checking the .isEnabled()
value, and then casts within the if.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
