Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
Description
The auto-export configuration doesn't order the rules correctly. It should assign highest precedence to the most specific path, but it doesn't. Instead, the highest prio is given to a shorter path, as described in the following e-mail:
Configuring the auto-export I'm attempting to export everything under /hst:hst to a module that's only bootstrapped on dev, except for 3 subtrees. Those three subtrees should be bootstrapped (and reloaded on startup) in production. Following the documentation [1] we have the following in pom.xml:
<sv:property sv:multiple="true" sv:name="hippo:contentpropset" sv:type="String">
<sv:value>content/local:/content</sv:value>
<sv:value>content/model:/hst:hst/hst:configurations/x</sv:value>
<sv:value>content/model:/hst:hst/hst:configurations/y</sv:value>
<sv:value>content/model:/hst:hst/hst:configurations/z</sv:value>
<sv:value>content/local:/hst:hst</sv:value>
<sv:value>content/model:/</sv:value>
</sv:property>The rule "content/local:/hst:hst" has the desired effect (everything under /hst:hst is exported to the module content/local). However, this rule also overwrites the three more specific rules above it. Those three rules have no effect unless we remove the previously mentioned rule. Re-ordering the rules doesn't help the cause.
Source: e-mail on hippo-dev with subject "Auto-export configuration: rules for subnodes".
Attachments
Issue Links
- relates to
-
CMS-8614 [7.9] Auto-export configuration: rules for subnodes
- Closed