Details
-
Improvement
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
Platform Sprint 144
Description
At this moment, at
/hippo:configuration/hippo:domains/defaultread/hippo-translation/type-hippo-translation
we bootstrap:
<sv:node sv:name="type-hippo-translation" xmlns:sv="http://www.jcp.org/jcr/sv/1.0"> <sv:property sv:name="jcr:primaryType" sv:type="Name"> <sv:value>hipposys:facetrule</sv:value> </sv:property> <sv:property sv:name="hipposys:equals" sv:type="Boolean"> <sv:value>true</sv:value> </sv:property> <sv:property sv:name="hipposys:facet" sv:type="String"> <sv:value>jcr:primaryType</sv:value> </sv:property> <sv:property sv:name="hipposys:filter" sv:type="Boolean"> <sv:value>false</sv:value> </sv:property> <sv:property sv:name="hipposys:type" sv:type="String"> <sv:value>Name</sv:value> </sv:property> <sv:property sv:name="hipposys:value" sv:type="String"> <sv:value>hippo:translation</sv:value> </sv:property> </sv:node>
The jcr:primaryType however can better be replaced by nodetype such that it also works for subtypes of translation (for example hippo taxonomy has subtyped the hippo:translation node)