Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#220 date_format ignored on 3.1.6

closed-works-for-me
httools (7)
5
2004-05-26
2004-05-07
nodata
No

I'm using ht://Dig 3.1.6.

In the config file, I have:
#iso_8609: true
date_format: %d/%m/%Y

On a webpage, I have:
<META NAME="htdig-notification-date"
CONTENT="02/06/2004">

I'm using British date formats.
ht://Dig is e-mailing me to say that the page is expired.

Any ideas?

Discussion

    • status: open --> closed-works-for-me
     
  • Logged In: YES
    user_id=149687

    See http://www.htdig.org/attrs.html#date_format
    and http://www.htdig.org/attrs.html#iso_8601
    as well as the description of htdig-notification-date
    in http://www.htdig.org/notification.html

    date_format only affects htsearch's output format, and not
    htnotify's input format. However, if you set iso_8601
    (not iso_8609) to true, it should coax htnotify into accepting
    the htdig-notification-date in the format you're using.

    Questions like this about configuration are best handled
    on the htdig-general mailing list, not in the bug database.

     
    • labels: --> httools
    • milestone: --> 102989
    • assigned_to: nobody --> grdetil
     
  • nodata
    nodata
    2004-05-10

    • status: closed-works-for-me --> closed
     
  • nodata
    nodata
    2004-05-10

    • milestone: 102989 -->
     
  • nodata
    nodata
    2004-05-10

    Logged In: YES
    user_id=960750

    Thanks for this, but I'm afraid it doesn't work.

     
  • nodata
    nodata
    2004-05-21

    Logged In: YES
    user_id=960750

    This actually works now.

     
  • nodata
    nodata
    2004-05-26

    • status: closed --> closed-works-for-me