[MGNLSTK-422] AllowedBodyClasses in BodyClassResolver.java should probably be configurable within STK? Created: 05/Aug/09 Updated: 25/Mar/13 Resolved: 25/Mar/13 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | concept |
| Affects Version/s: | 1.1.1 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Christian Ringele | Assignee: | Christian Ringele |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Description |
|
In the class info.magnolia.module.templatingkit.style.BodyClassResolver.java the allowed body classes are defined: ; If anything is configured by the user which is out of this definitions, a, error is generated in the log: This can be very easily achieved by changing the extrasArea.columns=2 (two extras areas).
I think it makes no sense, to provide by configuration possibilities which finally drag a need to subclass. |
| Comments |
| Comment by Christian Ringele [ 30/Dec/11 ] |
|
Here the same as with the TemplateAvailability. If needed you can change it easily in hte java class. |
| Comment by Christian Ringele [ 25/Mar/13 ] |
|
Correct status and fix version to set. |
| Comment by Christian Ringele [ 25/Mar/13 ] |
|
Already enough configurations in STK. |