We return the results from the search appliance through XML to another server on our domain, and everything has been working great.
However, I just recently updated to the newest texisScripts, and while I'm not sure if they are directly related, clicking on the results in our search pages has stopped working.
It looks like the problem is that the links are now being served to the "texis/search/redir.html" URL, but instead of serving them with the search server as the root, they are served as relative links, and as such, all the results are broken.
Is there a way to have the search results be presented as absolute links to the redirect page instead of relative links?
The "redir" is due to query logging being on so that clickovers can be logged. You can either turn off query logging or have the server that's publishing the results prepend something appropriate. Since you're republishing you'll also have to handle the redir requests on your server. The actual result url is encoded in the redir url as parameter named "u".
It would be appreciated if changes that have a potential to break all the search results would be documented properly. All I see in the maintenance window is "Provide proper in XML for query logging. ", which does not provide any indication of the consequences that this update has for everyone who does their own XSL transformation.
Are you planning to release a fix that presents results using absolute links anytime soon?
This was a fix that gave the proper url when query logging is enabled. In order to track the query logging results, it has to go through a redirect on the appliance. The problem before was that the plain URL was given when Query Logging is enabled.
If you want just the result URL in the xml results, you can disable query logging on the profile.
I do understand why it was implemented, but the fix introduced another more significant bug which will break all our pages. There is no simple fix that I can implement, and I have 250+ sites that use several different search appliances. Turning off query logging is not an option either in the long run.
