-
Bug
-
Resolution: Fixed
-
Neutral
-
4.4.1, 4.4.4
-
None
In case of using an extends feature for custom dialog definitions, one needs to reregister (i.e. server restart, or rename such dialog and name it back to its original name again) such dialog after update task of that module otherwise she will face http500 during its rendering (find the attachment).
Probably ExtendingContentWrapper and SystemContentWrapper are not so big friends each other.
Acceptance criteria
- is superseded by
-
MAGNOLIA-3732 SystemContentWrapper fails to wrap hierarchy manager of its node data
- Closed