edit node results in wrong date

I have a similar situation and had to disable the date popup.

I'll have a look at the format as well....

Yes, the setting for the format is the problem here, resetting it to '2009-09-10 19:11:11' fixes the default value upon edit....

Worked for me too. thanks guys.

The problem emerges when you choose a date string for the INPUT value, that is bound to change due to translations. E.g. if you choose an input string that contains the month name. Editing the node will give you the former value in the wrong language (e.g. Octobre instead of Oktober), which leads to the field not accepting the input and processing a default (or wrong) value.

So, how can I determine what format should I use? I tried the format advised by dagomar (04/09/2009 21:00), but it not works for me.
This bug is critical, because date fields not saved. If I set the date to any date and time value (using the popup calendar), and save the node, the node loses the data value and stays as empty.

That is a different error then, delykj. This issue is about loosing the data when editing.

That is a different error then, delykj. This issue is about loosing the data when editing.

OK, I will post a new issue.

+1

Anything new about this issue? I still have it.

See #5 for a way to fix it. Just change the INPUT date format.

+1 worked for me. Changed the input format @ nodetype-field.

Where is the INPUT date format? Is that the field located when you edit a nodetype?

Yes, it's in the field configuration, in other words, it's under /admin/content/node-type/{NodeTypeName}/fields/{FieldName}
There should be a dropdown list for input format.

i don't see how #5 is a solution. The field is a date field. Are you suggesting to change the intput type to a string?

No. If you just try it out, you will see that there is an "input format" drop down box which contains different formats for date values that can be entered. E.g. "1/24/2012" or "2012, January 24". The problem just appeared when this string contained translatable words (such as "January").

I'll admit that I was having some trouble because the date was not saving as I input it. Once I saw that it was consistently the same number of hours offset, I then realized, that there were timezone changes affecting my saved value. I went to my content type and adjusted the global settings for time zone handling so that instead of applying user time or site time, no time zone changes were applied.

This issue is getting old with no activity. I'm cleaning the issue queue, so I'll close this. Please feel free to reopen if needed!