For our intranet I've created a macro usable in the rte. The macro accepts an integer as an ID, consults our document management system for the document with that ID number, and returns a hyperlink to the latest version of that document.
xsltsearch appears to ignore the anchor text generated by the macro. It will recognise all the other text in the rte.
Is this the expected behaviour, or is there a setting in the xsltsearch xslt file that I can tweak? Failing that, any suggestions on how else to search the site?
You're right that in this scenario XSLTsearch will not 'see' the text the macro renders at runtime when the page is viewed in a browser. That's a limitation of how the content is stored in umbraco and thus its a limitation in XSLTsearch.
I'm not sure if Examine suffers the same limitation so it would be worth trying that. Examine is a great search engine though it can be more fiddly to set up and configure.
If both have the same limitation the alternative is to have a crawling indexer for the site that looks at the pages as they are rendered to the browser. A google search is an option. As is Microsoft's free Search Server Express. You might be able to include the results from such a crawler in Examine as well.
Okay...from what I can tell Examine has the same problem. I can generate results from the nodeName and bodyText properties...but it's still skipping over the generated anchor text.
Bother.
Right, time to investigate MS Search Server Express...
EDIT: According to Slace, Examine doesn't enter macro rendered content into its index by default, though it is possible to hook into some events and add this behaviour (though its a non-trivial problem).
What I've remembered, however, is that my macro uses the User's Active Directory credentials to pull the relevant info from the DMS to build the hyperlink, so getting the data into the index would be...tricky. So, I'm pretty sure at this point that I'm not going to be able to get it working whatever I do, at least in the allocated project time.
xslt search of text generated by rte macro?
For our intranet I've created a macro usable in the rte. The macro accepts an integer as an ID, consults our document management system for the document with that ID number, and returns a hyperlink to the latest version of that document.
xsltsearch appears to ignore the anchor text generated by the macro. It will recognise all the other text in the rte.
Is this the expected behaviour, or is there a setting in the xsltsearch xslt file that I can tweak? Failing that, any suggestions on how else to search the site?
Hi!
It sounds like this should work but when it comes to searching an Umbraco site I perfer using Examine, have a look at this:
http://farmcode.org/post/2009/04/20/Umbraco-Examine-v4x-Powerful-Umbraco-Indexing.aspx
http://maanehunden.wordpress.com/2010/07/23/how-i-made-umbraco-search-with-lucene-indexing-eximine-and-xslt/
Hi, Jon,
You're right that in this scenario XSLTsearch will not 'see' the text the macro renders at runtime when the page is viewed in a browser. That's a limitation of how the content is stored in umbraco and thus its a limitation in XSLTsearch.
I'm not sure if Examine suffers the same limitation so it would be worth trying that. Examine is a great search engine though it can be more fiddly to set up and configure.
If both have the same limitation the alternative is to have a crawling indexer for the site that looks at the pages as they are rendered to the browser. A google search is an option. As is Microsoft's free Search Server Express. You might be able to include the results from such a crawler in Examine as well.
Let us know how you get on.
cheers,
doug.
Thanks guys.
I'll have a look at Examine to start with and see how I go. I'll let you know what I end up with.
Cheers
Jon
Okay...from what I can tell Examine has the same problem. I can generate results from the nodeName and bodyText properties...but it's still skipping over the generated anchor text.
Bother.
Right, time to investigate MS Search Server Express...
EDIT: According to Slace, Examine doesn't enter macro rendered content into its index by default, though it is possible to hook into some events and add this behaviour (though its a non-trivial problem).
What I've remembered, however, is that my macro uses the User's Active Directory credentials to pull the relevant info from the DMS to build the hyperlink, so getting the data into the index would be...tricky. So, I'm pretty sure at this point that I'm not going to be able to get it working whatever I do, at least in the allocated project time.
Lower tech solution, here we come.
is working on a reply...