Uploaded image for project: 'Magnolia Standard Templating Kit (closed)'
  1. Magnolia Standard Templating Kit (closed)
  2. MGNLSTK-972

ThemeInstallTask should not depend on an existing theme configuration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Outdated
    • Major
    • 2.0.x
    • 1.4.7, 2.0, 2.0.1, 2.0.2, 2.0.3
    • themepop
    • None

    Description

      The ThemeInstallTask expects an existing Theme configuration within the module's bootstrap files.

       new BootstrapSingleResource("", "", "/mgnl-bootstrap/theme-" + themeName + "/config.modules.standard-templating-kit.config.themes." + themeName + ".xml", ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING).execute(ctx);
      

      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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                cringele Christian Ringele
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: