Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-5529 Update mechanism improvements
  3. MAGNOLIA-3258

installation/update: execute tasks after a later installation of an optional module

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: modulemechanism
    • Labels:
      None

      Description

      In several place we define installation tasks which should only be executed if a certain module is installed. This is currently possible by using IsModuleInstalledOrRegistered.

      example: workflow module changes the dms configuration on installation

      The problem is, that if a module is marked as being optional (dms), it can be installed at a later moment long after the installation tasks of the module (workflow) where executed.

      The solution would be to register this kind of tasks explicitly as being dependent on an other module and execute them only after the installation of the module.

      Note: we also started to introduce so called bridge modules which only deliver the tasks executed in such a scenario. While it complicates bundling and other things it is still likely that one forgets to install the bridge module.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              pbaerfuss Philipp Bärfuss
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: