I've setup htdig 3.2.0b6 and 3.1.6 on both Solaris 8 and Redhat 9 trying to get use_doc_date to work with my CGI scripts that output HTML. I've applied the recommended patch to the 3.1.6 as described here: http://www.htdig.org/mail/2000/04/0156.html

I don't know much about this patch, but it looks like it was for 3.1.5. It
is possible that it is not applicable to 3.1.6.


There is a more important patch for 3.1.6. There is a parsing problem with
the code in the default distribution that is corrected with the following
patch.


ftp://ftp.ccsf.org/htdig-patches/3.1.6/metadate.0

My apologies, that is the patch we used. I referred to the wrong archived mail-list message. Still no change.



I've been going nuts for two days and must be missing something simple or possibly misunderstanding the function of use_doc_date.

In my htdig.conf file I have the following lines:
# use meta date to determine a new page
use_doc_date: true

Within the head of each of the pages indexed I have something like this:
<META NAME="Date" CONTENT="2005-02-16">


I've tried using META name dc.date, dc.date.created and dc.date.modified. I've also tried dates in the format YYYYMMDD, YYMMDD, YYYY-MM-DD HH:MM:SS, YYYY MM DD, etc....

You are reindexing after each change aren't you?

I'm reindexing after each change with a modified version of rundig that doesn't use the -i flag for htdig (I've also disabled the -a flag for the modified rundig). I've tried using the default rundig as well. No luck.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ht://Dig general mailing list: <[email protected]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general

Reply via email to