-
Bug
-
Resolution: Duplicate
-
Minor
-
5.0
-
None
-
Magnolia 5 with workspaces using Jackrabbit 1.5+
When firing a JCR query, the resulting node order does not reflect the order in their JCR tree (e.g. as displayed in a content app). The reason is that Jackrabbit's attribute "respectDocumentOrder" is false by default (version 1.5+) for performance.
Solution
In a workspace's workspace.xml inside the SearchIndex tag, add
<param name="respectDocumentOrder" value="true"/>
Acceptance criteria
- duplicates
-
-
- Closed
-
