Details
Description
Currently, each module listed in the AutoExport configuration has one or more paths for which it receives the content and config definitions. The 'development' module as generated by the archetype should only receive updates for content definitions that it owns itself. Any config definitions the dev should move/create there manually.
A temporary workaround could be to configure a non-existing path as root node for the 'development' module.
Attachments
Issue Links
- relates to
-
REPO-1768 AutoExport does not validate its module configuration when starting up disabled
- Closed