Is the search result someplace public that we could see? Otherwise we'll need to open a ticket to see exactly what XML and XSL are being used to figure out what's going on.
Additional Fields XML namespace changed
Additional Fields XML namespace changed
I just submitted a ticket.
Additional Fields XML namespace changed
For those reading this later, we've determined that the original namespace I suggested was incorrect - it should be
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:u="http://www.thunderstone.com/ParametricSearch/1.0/">
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:u="http://www.thunderstone.com/ParametricSearch/1.0/">
Additional Fields XML namespace changed
Jason,
when do you think the issue with the multiple dates might be resolved, or is there a workaround? We are anxious to update our scripts to resolve an unrelated issue, but won't be able to do so unless the dates are handled correctly.
Thanks
ds
when do you think the issue with the multiple dates might be resolved, or is there a workaround? We are anxious to update our scripts to resolve an unrelated issue, but won't be able to do so unless the dates are handled correctly.
Thanks
ds
Additional Fields XML namespace changed
As a workaround, you should be able to extract the date from the content of the page where it says
Publish date: Jul 16, 2008
In the Data From Field section, set REX Search to "Publish date: \P=!$+" (without the quotes) and From Field to "Text".
Publish date: Jul 16, 2008
In the Data From Field section, set REX Search to "Publish date: \P=!$+" (without the quotes) and From Field to "Text".
Additional Fields XML namespace changed
Jason,
is there a solution for the problem related to the date being retrieved multiple times? The workaround that I implemented is creating other troubles now...
is there a solution for the problem related to the date being retrieved multiple times? The workaround that I implemented is creating other troubles now...
Additional Fields XML namespace changed
There currently isn't one yet; I'll step up the investigation of it to see if we can figure out what's going on with it.
Additional Fields XML namespace changed
Is texisScripts 6.3.5 supposed to fix this? It looked like it would, but so far I have had no luck, the date is not parsed from the meta field...
Additional Fields XML namespace changed
Correct, it looks like meta values are not currently overriding HTTP values; these will get swapped in an update.
Additional Fields XML namespace changed
Actually I take that back, I was looking at the wrong date in my test. It appears to be working here. When I request the URL
http://www.modernmedicine.com/modernmed ... ail/497285
And store last-modified in a custom additional field,
it correctly gets 2006-11-15 00:00:00
Are you sure the page is being rewalked?
http://www.modernmedicine.com/modernmed ... ail/497285
And store last-modified in a custom additional field,
it correctly gets 2006-11-15 00:00:00
Are you sure the page is being rewalked?