We have a lot of users who register at the very last minute. Often, when they try to register for an event on the day of the event, but before the event has started, CiviCRM tells them registration is closed.
I'm surprised that by default registration closes for an event before the event starts. Surely the default is that you can register for an event right up to the configured start time?
I was wondering if this might be due to a time zone issue on the server. Is there a right way to set the date on the server side? It is currently 6:40 pm Pacific where our organization is. If I do a
date command on our server, I get:
Tue Jan 11 02:40:02 UTC 2022.
I don't see anywhere in CiviCRM administration screens that I can see what it thinks the current date/time is. Is there such a place?
If I look in Drupal's status report, I see this:
The timezone has been set to America/Vancouver. and if I go to Drupal's
/admin/config/regional/settings configuration I do see that it says the current date and time in our office's location. And if I look at Drupal recent log messages, it lists a log message with a date/time within 1 minute of the current time.
So that all indicates to me that Drupal (and I presume Civi) knows the correct date & time at our office.
So then why can't a user register for an event on the day of the event but an hour or two before it has started?
(I know I can fix this by just setting the "Registration End Date" field in the Online Registration tab to the day after the event starts, for example, but this is annoying to have to set for every event, I often forget to set it right, and it just "feels wrong" that this should be happening.)