[MGNLSTK-1004] Extras area deprecated code for "module" Created: 27/Sep/12 Updated: 13/Jun/16 Resolved: 07/Jun/16 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | templates |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | 2.9 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Natascha Desmarais | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | deprecation-free | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: | |
| Sprint: | Kromeriz 47 |
| Description |
|
In info.magnolia.module.templatingkit.templates.ExtrasArea we provide a deprecated method called setModule(..). The problem with this method is that it silently allows wrong (old) structuring of the extras area. Right now if you want to enable the module part, you can do it in 2 ways: follow the correct structuring extras > areas > module or extras > module. This is confusing since this only works for the module and not for extras1 and 2. Instead of working silently, we should log a warning (or exception) that the configuration should be upgraded to the newest layout. Or let it still work, but add the warning/exception. |
| Comments |
| Comment by Christopher Zimmermann [ 07/Oct/13 ] |
|
Agree - Instead of working silently, we should log a warning (or exception) |
| Comment by Milan Divilek [ 07/Jun/16 ] |
|
Deprecated method was removed in STK-2.9 ( |