I have a series of nodes that i am using to display data on a parent page. The actual folder structer is:
Page - Page Features -- Feature A -- Feature B
The Page Features folder is hidden from the nav so i created a seperate field for excluding items from the nav and added it to the macro call, but i'm still not able to get results from the Feature Nodes. Is there any way to get results from those features?
The exclusion of "Data nodes" is actually by design as how would you render a page that doesn't have a template? My usual suggestion is that, if you using data nodes, you are probably linking them to a page that does have a template, so you should hook into Examines GatheringNodeData event (take a look in the ezSearch bootstrapper for an example) and if indexing the parent node, gather the contents from the data nodes, and stuff it into the "content" field so that the parent page shows up for searches that match data on the data nodes.
That said, if you must have your data nodes show up, you can modify esSearch.cshtml and remove any occurences of "-template:0" and your results should then show up.
Thanks for the quick replay Matt, I suspected that they weren't being shown because they didn't have templates and that certainly makes sense. I feel a bit dumb asking this but could point me to the bootstrapper?
Thanks and great job on this package, xsltsearch was integral to many of the sites i had built in v4 so it's nice to see the collaboration between you and Doug to make an awesome updated version.
No problem, the boostrapper is just a .cs script installed with ezSearch (it combines fields onto one content field for easy searching, along with a couple of other things). You should find it in your App_Code folder (ezSearchBoostrapper.cs).
Have a look in there and it should hopefully point you in the right direction.
The query ezSearch generates is a raw Lucene query, so you should be able to use any of the standard lucene query syntax (http://lucene.apache.org/core/2_9_4/queryparsersyntax.html). In terms of that specific query "-tempalte:0" that is basically saying to exclude any item who's template field is 0 (so basically any item with no template).
I hate to bring a answered thread to life, but I am wanting data nodes to be indexed and return the parent page.
I looked at the bootstrap c# file, but it didn't really give me an indication on how to do this.
Does anyone have an example of how they may have implemented this?
I have a documentType called "Image-Title-Content" and I use this to add a repeater-row like affect for repetitive content and the properties to be included on the index are "itcTitle" and "itcContent".
No results from child nodes used for data
I have a series of nodes that i am using to display data on a parent page. The actual folder structer is:
Page
- Page Features
-- Feature A
-- Feature B
The Page Features folder is hidden from the nav so i created a seperate field for excluding items from the nav and added it to the macro call, but i'm still not able to get results from the Feature Nodes. Is there any way to get results from those features?
Hi Owen,
The exclusion of "Data nodes" is actually by design as how would you render a page that doesn't have a template? My usual suggestion is that, if you using data nodes, you are probably linking them to a page that does have a template, so you should hook into Examines GatheringNodeData event (take a look in the ezSearch bootstrapper for an example) and if indexing the parent node, gather the contents from the data nodes, and stuff it into the "content" field so that the parent page shows up for searches that match data on the data nodes.
That said, if you must have your data nodes show up, you can modify esSearch.cshtml and remove any occurences of "-template:0" and your results should then show up.
Many thanks
Matt
Thanks for the quick replay Matt, I suspected that they weren't being shown because they didn't have templates and that certainly makes sense. I feel a bit dumb asking this but could point me to the bootstrapper?
Thanks and great job on this package, xsltsearch was integral to many of the sites i had built in v4 so it's nice to see the collaboration between you and Doug to make an awesome updated version.
Owen
Hi Owen,
No problem, the boostrapper is just a .cs script installed with ezSearch (it combines fields onto one content field for easy searching, along with a couple of other things). You should find it in your App_Code folder (ezSearchBoostrapper.cs).
Have a look in there and it should hopefully point you in the right direction.
Matt
Hello Matt,
Bit off topic but where is it documented what "-template:0" exactly means and what other query settings are possible in Examine ?
Thanks in advance and thanks for a very handy package !
Teus
Hi Teus,
The query ezSearch generates is a raw Lucene query, so you should be able to use any of the standard lucene query syntax (http://lucene.apache.org/core/2_9_4/queryparsersyntax.html). In terms of that specific query "-tempalte:0" that is basically saying to exclude any item who's template field is 0 (so basically any item with no template).
Hope that helps
Matt
Thanks Matt, that's just what I was looking for!
Regards
Teus
I hate to bring a answered thread to life, but I am wanting data nodes to be indexed and return the parent page.
I looked at the bootstrap c# file, but it didn't really give me an indication on how to do this.
Does anyone have an example of how they may have implemented this?
I have a documentType called "Image-Title-Content" and I use this to add a repeater-row like affect for repetitive content and the properties to be included on the index are "itcTitle" and "itcContent".
Many thanks
Phillip
is working on a reply...