Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
None
Description
Moving configuration can break Magnolia. Today we needed to use the Rescue app for a customer to move the /modules/dam-app node from /modules/dam-images/dam-app back to /modules because someone did move the module node by accident.
During startup, Magnolia could not vind the config for the dam-app module and started the auto-updater. The first Task failed due to a ItemExistsException because the config is there, but moved into different location.
Magnolia will fail to start up, and enabling the Rescue app was needed.
Steps to reproduce
- Open Configuration app
- Expand /modules/
- Drag dam-app below other module
- Restart Magnolia
.. Logs, screenshots, gifs...
Expected results
When moving the dam-app node, a confirmation dialog should be shown to warn the user of the action and to confirm the move.
Actual results
Without any notification, the node is moved
Workaround
Development notes
Checklists
Acceptance criteria
