Uploaded image for project: 'Content Dependencies'
  1. Content Dependencies
  2. MGNLCDEP-121

Migration from Magnolia 5 to 6 gives NoClassFoundExceptions on DependencyAwareConfirmationActionDefinition

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Neutral
    • None
    • None
    • None

    Description

      Steps to reproduce

      1. Bootstrap a Magnolia 5 instance with the content dependencies module.
      2. Boot a Magnolia 6 on the resulting repository

      This yields several NoClassFoundExceptions for the class 

      info.magnolia.module.dependencies.action.DependencyAwareConfirmationActionDefinition

      These come from the Magnolia 5 apps still configured in JCR for pages and assets.
      Namely the two following paths:

      • /modules/pages/apps/pages/subApps/browser/actions/confirmDeletion
      • /modules/dam-app/apps/assets/subApps/browser/actions/confirmDeleteAsset

      It appears that the configuration for these apps is not corrected for the new version (or rolled back to the non-dependencies version).

      Workaround:

      Set the class to info.magnolia.ui.framework.action.DeleteConfirmationActionDefinition and remove the references subnode.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              rico.jansen Rico Jansen
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD