Closed (fixed)
Project:
Date
Version:
5.x-2.0-rc2
Component:
Date CCK Field
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Jul 2008 at 15:19 UTC
Updated:
31 Jul 2008 at 04:47 UTC
I have a node with two date fields. The first one has a start and end date, uses multiple dates, and goes down to minutes. The second field is a single date, uses no multiple dates, and goes down to days.
The second date will revert to January 1, 2008 when I save, no matter what I set in the edit field. The first date works perfectly.
I think it is a bug introduced later than date-5.x-2.0-rc. I first noticed this bug when I upgraded to date-5.x-2.0-dev two days ago. Before that I had only used date-rc.
This bug is 100% reproducible in every single node I create using this field.
Comments
Comment #1
karens commentedThis may be the same as http://drupal.org/node/273344, which I've never been able to reproduce.
Can you export the fields info (using Content Copy) and tell me what version of PHP, MYSQL, etc you are using.
Comment #2
will_in_wi commentedMySQL database 5.0.51a
PHP 5.2.6
Web server Apache/1.3.34 Ben-SSL/1.55
Anything else?
Comment #3
will_in_wi commentedIt looks like it could be similar to #273344: Date Popup inserts wrong dates for empty dates. Not sure though.
Comment #4
karens commentedYay! I can reproduce the problem finally! Now I can try to find the fix. Thanks :)
Comment #5
karens commentedThis turned out to be the perfect example for fixing this because you had one field that had the original problem I was trying to fix and one that got broken by the fix. I fixed the fix and it broke the first date again, but then I found a way to fix both. Hopefully all is well now :)
Thanks!
Comment #6
will_in_wi commentedIt works for me! Thanks! That was really quick!
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.