-
Improvement
-
Resolution: Fixed
-
Major
-
2.4.2
-
None
-
-
Empty show more show less
-
Basel 25
-
0
With the changes in MAGNOLIA-6338, we are able to observe added/deleted resources, however, current implementation of ResourceContainer is not able to react to this change. When one would delete a resource which is only available in one of the origins, then resourcesApp would throw an exception but instead it should be deleting the row from the view.
ResourcesContainer should be reflecting the changes for any given resource files.
Acceptance criteria
- is related to
-
MAGNOLIA-6338 New template scripts on the classpath are not loaded
- Closed
-
MGNLRES-192 Renaming a resource in the file system causes a running resources app to throw exception
- Closed