ThemeInstallTask should not depend on an existing theme configuration
---------------------------------------------------------------------
Key: MGNLSTK-972
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-972
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: themepop
Affects Versions: 2.0.3, 2.0.2, 2.0.1, 2.0, 1.4.7
Reporter: Christian Ringele
Priority: Major
Fix For: 2.0.x
The ThemeInstallTask expects an existing Theme configuration within the
module's bootstrap files.
{code}
new BootstrapSingleResource("", "", "/mgnl-bootstrap/theme-" + themeName +
"/config.modules.standard-templating-kit.config.themes." + themeName + ".xml",
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING).execute(ctx);
{code}
When creating a new theme, there can't exist a theme configuration yet.
This is one of the most often stumbles for people when creating a custom theme.
The ThemeInstallTask should use a custom task, which first checks if the
resource exists within the jar/module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
