Hi,

I'm using Drupal 5.1 with Php 5.2.0-8+etch13

For the longest time, with the old date module, I had an issue with dates before 1970 where the date would decrement every time a node was edited. This got fixed when I installed the new 5.x-2.5 version of Date.

Unfortunately, I now have a cck date field that accepts years that has started showing a similar problem for dates before ~1750. Every time the node is edited, the year decreases by one.

The only other suspicious update I've made recently is to the node_import module because the version I had was not importing the to-date correctly. This update did change something in Date. Do you think that may have triggered the problem?

Would installing the newer dev version of Date on this live site help with this issue?

I have a lot of nodes with dates before 1750, and this is a big problem, especially since I've been entering a lot of historic data thinking that the problem would not occur.

Please help!
ktnk

CommentFileSizeAuthor
#2 issue-397432-Year field export.txt2.66 KBktnk

Comments

ktnk’s picture

ktnk commented
Title: Old Dates automatically change wenever nodes a edited » Old Dates automatically change wenever node is edited
ktnk’s picture

ktnk commented
StatusFileSize
new issue-397432-Year field export.txt2.66 KB
samuelsov’s picture

samuelsov commented
Status: Active » Needs review

After working on this, I think it is a problem with timezone. In the field, the Time zone handling is set to No time zone conversion and yet, if i go the date_local_date function (in date_elements.inc), it calls date_timezone_set($date, timezone_open($timezone));

To fix this problem, i have added a condition on line 250 :

    if ($field['tz_handling'] != 'none') {
      date_timezone_set($date, timezone_open($timezone));
    }
samuelsov’s picture

samuelsov commented

Same problem in date_combo_validate...

ktnk’s picture

ktnk commented

Thanks, This solution works well so far.

However, A related issue is that if I change my date display as "Time Ago" even on nodes that have full dates rather than just a year, then my "time ago" value will always be off by a few days.

ktnk.

karens’s picture

karens commented
Status: Needs review » Fixed

This has since been fixed in -dev.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.