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

Register some sort of RecoveryFilter for when the filter chain is not correctly configured

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Major
    • None
    • 4.1
    • core
    • None

    Description

      Currently, if no filter chain is available, we end up with ugly NPEs.

      If the /server/filters node is not available at all, we could for instance instanciate rootFilter as some sort of filter that lets Magnolia start and give the user a chance to fix the installation.

      Another issue is that activation is obviously broken if the filter configuration is broken. The following scenario needs to be taken into account:

      • filters broken on author
      • user decides to delete the filter nodes and reimport a backup. If not careful (and if we still have the deletion=immediate deactivation), the filters are also removed from the public instance.
      • if the import succeeds (which will probably need a restart anyway for the filters to be reinitialized), the imported configuration still can't be activated to the public instance(s), since those have no filters - thus no activation filter.

      TODO - there are related issues, link and/or fix them !

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD