Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-2445

Error in install/update still allows Magnolia to startup (and thus most likely fail miserably) when magnolia.update.auto is set to true

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 3.6.3
    • core, updatemechanism
    • None

    Description

      The exception handling is different depending on which ModuleManagerUI is used (in ModuleManagerNullUI, everything happens in onStartup(), which is called in ConfigLoader, while in ModuleManagerWebUI, everything happens in calls to execute(), which are called by the InstallFilter)

      In both cases, Magnolia should not start if the install or update was unsuccessful. We only need to figure out what to with incoming http requests, when using ModuleManagerNullUI. This is very much related to MAGNOLIA-2244 which asks for a review/cleanup/removal of the ConfigLoader.isBootstrapping(), .isConfigured() and .enterListeningMode() methods !

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                pbaerfuss Philipp Bärfuss
                gjoseph Magnolia International
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD