Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Any booking made with MERCI is +3h our local timezone (AST). Any regular posts, including the reservation posting, have proper time stamp, so it doesn't seem to be a site wide issue. It just changes the actual reservation time to add 3 hours. This also coincides with UTC. Any ideas what MERCI is becoming tangled on?
Thx
Nathan
Comments
Comment #1
darrick CreditAttribution: darrick commentedDo you have a default timezone set at admin/settings/date-time
Comment #2
nscad_nathan CreditAttribution: nscad_nathan commentedThanks for the reply:
Timezone is set to
America/Halifax
(correct for us) and user configurable TZ isdisabled
, fist day of the weekSunday
Follow up:
Out of curiosity I changed my sites TZ to
Europe/London
and now I have the opposite problem - creation data is +3h of where it should be (correct for UTC) and now reservation time is correct as entered!. So, apparently something is not clicking between MERCI and the TZ setting of my site.Any other ideas?
Comment #3
kreynen CreditAttribution: kreynen commentedI was able to reproduce Nathan's error with these steps...
The work around is really simple and is likely why we never saw this. I disabled MERCI, uninstalled it, and reinstalled it and no longer see the error. Unfortunately that fix deletes all nodes in MERCI enabled content types and the content type settings so you'd have to configure those again.
I think the real issue is adjusting the timezone after MERCI is installed, but I'm not sure why.
Comment #4
kreynen CreditAttribution: kreynen commentedLock/unlock feature added to the merci admin settings page. Unlocking the mecri_date field and editing it using CCK's Manage Fields (even if every option stays the same) fixed the problem for me.
Needs more testing.