|
Matija Boban
|
November 11, 2024 at 9:03 pm
when anyone register for the event the time showing in “all attendees” is not matching with the actual time
Because I am getting email notification at the same time,
The attendee page is 1 hour ahead of us. The time for “Habonne” should be 10:05am instead of 11:05am.
|
|
Garth
|
November 12, 2024 at 9:22 am
Hi Matija,
How are you today?
Event Espresso time settings are set by what you have configured in the WordPress. What are your WordPress Timezone settings in WordPress > General Settings > Timezone?
|
|
Matija Boban
|
November 13, 2024 at 10:49 pm
Even though the time difference is one hour our courses are still closing 7 hours in advance…..so we need to change the registration end date to the day after the course to allow the course to still be posted the night before (which takes a lot of time).
time zone is already updated its UTC-4 now
|
|
Matija Boban
|
November 18, 2024 at 10:21 pm
I am waiting for response from support team to fix the issue on my live website.
|
|
Tony
|
November 19, 2024 at 7:21 am
Hi there,
Apologies for the delay.
With issues like this what is usually happens is another plugin is calling date_default_timezone() which changes the servers timezone, WordPress expects the timezone to be set to UTC and then it applies offsets to that timezone to display the correct dates/times. Using the above function breaks dates in all sorts of weird ways becuase offsets are applied to values where the timezone has already been applied etc.
time zone is already updated its UTC-4 now
So it’s set to ‘UTC-4’ and not a location?
Your site is currently using 3.1.37.3.P but you’ve updated to the latest version of WordPress. A long time ago now WordPress (version 5.3+) introduced changes to how WordPress core handles datetimes internally and we released version 3.1.37.17.P to work around those so with the version you are currently running you are likely still running into those as well.
—-
You’re likely going to spend a fairly significant amount of time catching up on the missed EE3 updates that have not been applied to the site here (3.1.37.3.P was released May 6, 2015).
Can you not switch to EE4? I suspect the time spent working through this would be better spent switching to EE4 as that’s the current supported version.
|
