[MGNLSTK-1494] Custom themes are not migrated Created: 24/Jul/15 Updated: 15/Apr/16 Resolved: 12/Aug/15 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | 2.9 |
| Fix Version/s: | 2.9.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Jan Schulte | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | backlog541, support | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1h 55m | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Date of First Response: | |||||
| Sprint: | Sprint 5 (Kromeriz) | ||||
| Story Points: | 2 | ||||
| Description |
|
The migrate theme task is private. It seems that existing non magnolia themes are not automatically migrated. Seems like the MigrateThemeTask can't be called by customers as it is a private inner class. private class MigrateThemeTask extends NodeExistsDelegateTask { public MigrateThemeTask(final String themeName) { super( String.format("Copy %s theme to its new home", themeName), String.format("/modules/site/config/themes/%s", themeName), new WarnTask("Warn about already existing theme", String.format("Could not copy '%s' theme to new site module. Check you configuration at /modules/site/config/themes/%s", themeName, themeName)), new ArrayDelegateTask("", new CopyNodeTask(String.format("Copy %s theme to its new home", themeName), String.format("/modules/standard-templating-kit/config/themes/%s", themeName), String.format("/modules/site/config/themes/%s", themeName), false), new CheckOrCreatePropertyTask("", String.format("/modules/site/config/themes/%s", themeName), "class<span class="code-quote">", "info.magnolia.module.templatingkit.style.ThemeImpl") ) ); } } |
| Comments |
| Comment by Richard Gange [ 24/Jul/15 ] |
|
Workaround: add class=info.magnolia.module.templatingkit.style.ThemeImpl to /modules/site/config/themes/yourTheme |