[MGNLSTK-951] Disabling ExtrasArea without need to define class property: BodyClassResolver should first check if enabled, then cast. Created: 15/May/12 Updated: 06/Jun/12 Resolved: 15/May/12 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | base system, themepop |
| Affects Version/s: | 2.0, 2.0.1, 2.0.2 |
| Fix Version/s: | 2.0.3 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christian Ringele | Assignee: | Ondrej Chytil |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Patch included: |
Yes
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Disabling the extras area is the most common use case on templates, besides reconfigure it. The new code uses first a default AreaDefintion for checking the .isEnabled() value, and then casts within the if. |
| Comments |
| Comment by Christian Ringele [ 15/May/12 ] |
|
Would be nice if this could be applied ASAP. |
| Comment by Ondrej Chytil [ 15/May/12 ] |