OK Kevin, thanks.I have been experimenting with PATH searches in FreeMarker templates and I must admit I'm still confused.I put the following line in a template:
<#list companyhome.childrenByLuceneSearch["PATH:\"//cm:generalclassifiable//cm:D6Activity//cm:M4//cm:M4QoE//member\""] as member>
and I expected it to yield a list of all the documents that had been categorized as M4QoE. I know there are 4 documents that fullfill this requirement, but all I got was an empty list. (At least, it was not an error message. )Now, this could be due to two reasons. Either I abused the search string, or the string did produce the four documents, but I was unable to "catch" them. The reason for my confusion is that I'm not sure if I understood the term "member" in the Search#Category_Queries wiki page. Is it correct that there IS a child relationship between category and its subcategories, but that actual documents are members and not children? If so, 1. why does the following freemarker script not produce a list of the subcatories of the "D6Activity"?
<table>
<#list companyhome.childrenByLuceneSearch["PATH:\"//cm:generalclassifiable//cm:D6Activity//*\""] as child>
<tr><td>${child}</td></tr>
</#list>
</table>
2. 1. why does the following freemarker script not produce a list documents?
<table>
<#list companyhome.childrenByLuceneSearch["PATH:\"//cm:generalclassifiable//cm:D6Activity//cm:SDRFLAI//member*\""] as member>
<tr><td><a href="/alfresco${member.url}" title="Download this file">${member.properties.name}</a></td></tr>
</#list>
</table>
Or, do these PATH search string always have to be combined with TEXT searches as in the web interface?Ludo
