Just updated to 2.6. When editing content with datestamp field there is a major problem: instead of displaying real dates for already existing date values (multiple dates enabled for field) current date/time showed. Help plz - we're unable to change anything on calendar, downgrading to 2.5 doesn't make the things better - calendar view displayed empty.

CommentFileSizeAuthor
#5 date_widget_type.patch709 bytesv1nce
#3 date_widget_type.patch714 bytesscottgifford

Comments

leoric’s picture

leoric commented

Reverting to 2.5 for now. Just recollected that the reason of empty calendar is buggy "Unlimited" option for "Maximum items" setting in calendar setup.

v1nce’s picture

v1nce commented

We are seeing a similar issue with a date field that has to/from popup calendar widgets as well. When editing a node, the default_value resets to the current date/time instead of the originally submitted value.

scottgifford’s picture

scottgifford commented
StatusFileSize
new date_widget_type.patch714 bytes

I encountered this problem too, it seems to happen when using a datestamp type. The problem seems to be in the conversion from the database field to a date object; instead of converting from the type in the field, it was always converting from a DATETIME type.

The attached patch fixed the issue for me.

pschopf’s picture

pschopf commented

Thanks, it worked for me as well.

v1nce’s picture

v1nce commented
Status: Active » Reviewed & tested by the community
StatusFileSize
new date_widget_type.patch709 bytes

Looks good. Thanks.

Updated patch to use correct path in patch for original file.

leoric’s picture

leoric commented

Thanks, seems to work fine after applying patch!

cangeceiro’s picture

cangeceiro commented

applied patch and it fixed it

dalin’s picture

dalin
he/him
Primary language English
Location 🇨🇦, 🇲🇽, 🌍
commented

patch in #5 works for me too.

kaare’s picture

kaare
him/his
Primary language Norwegian Bokmål
Location Tromsø
commented

I can confirm both the bug and that the patch in #5 works.

dperdue’s picture

dperdue commented

Had problem, patch in #5 worked for me as well.

jamestombs’s picture

jamestombs commented

Patch #5 worked for me too.

karens’s picture

karens commented
Status: Reviewed & tested by the community » Fixed

Actually the fix goes the other way, all element handling should be in DATETIME formats rather than the field['type']. A slightly different patch committed. Thanks!.

scottgifford’s picture

scottgifford commented

Your fix in the latest version works perfectly. Thanks!

Status: Fixed » Closed (fixed)

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