while the events list shows the am / pm time after i have set the 12 hour clock in the event module settings, the calendar still shows 24 hour time.

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented
Assigned: Unassigned » killes@www.drop.org

I think I fixed it. Please confirm.

erikhopp’s picture

erikhopp commented

when the 12h clock is selected in the event module settings, it still shows up as a 12h clock in the upcoming events listing, but the 24h clock in the calendar.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

This bug is still present in 4.4.0.

rightchristians’s picture

rightchristians commented

I'm having the same problem with an otherwise easy and succesful installation.

killes@www.drop.org’s picture

killes@www.drop.org commented

I think it is fixed now. Please close if true.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

Almost - Times with minute components show up like "7pm 05". $date_format = t('g:ia'); works better...

Thanks!

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

Whoa, wait a minute - did something change in this version in timezone handling? Old events display with the times I entered, but when I enter a new event it's 5 hours off. Strangely, I was on GMT-5 (EST), but I still see new events coming through as 5 hours off even after setting both my account setting and the Drupal configuration setting to GMT-4 (EDT).

If I disable "Timezone handling" in the event module configuration, new events display at the same time they were entered, but the previous events are all wrong....

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

It looks like the $date_format change is in CVS, thanks!

Given that the site I'm converting to Drupal is a neighborhood site (so pretty much anyone interested in it should be viewing event times as Eastern US), "No" seems to be the proper "Timezone handling" setting. Since apparently the start time is saved as Unix timestamps (digression: why does the Drupal style seem to avoid SQL DATETIME fields?), I was able to fix my past events with the query

update event set start=start-(5*60*60);

Anyone else looking to fix up their events, substitute your own timezone differential for the "-(5" part of that query...

killes@www.drop.org’s picture

killes@www.drop.org commented

Note: The "timezone handling" feature in the head branch is purely experimental and still unfinished. In particular it will not work with daylight savings time and may be changed without notice. I plan to convert this setting to usesql fields instead of timestamps.

Anonymous’s picture

(not verified) commented