[MGNLSTK-976] Update to STK 2.0 overrides the custom theme installed Created: 20/Jun/12 Updated: 26/Jul/12 Resolved: 25/Jul/12 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | update |
| Affects Version/s: | 2.0.x |
| Fix Version/s: | 2.0.4 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Samuel Schmitt | Assignee: | Ondrej Chytil |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Description |
|
If you have custom themes installed in {{ /modules/standard-templating-kit/config/themes}} they are overridden by an update task of STK 2.0. Who is the culprit? .addTask(new BootstrapSingleModuleResource("Configure themes","Bootstrap the new pop and pop-mobile theme","config.modules.standard-templating-kit.config.themes.xml")) We must rather bootstrap pop and pop-mobile separately than the whole themes node. |