|
Joachim Schmidt
|
November 2, 2015 at 1:52 pm
Hi, WordPress set to Zurich.
Calendar add-on and event list show correct time.
event and upcoming event widget show +1h for eac event.
event +1h
upcoming events widget +1h
calendar add-on correct time
event list correct time
|
|
Tony
|
November 3, 2015 at 6:29 am
Hi there,
Can you tell me the date and time format you are using within WordPress please?
Did you create these events before or after setting the timezone to Zurich?
|
|
Joachim Schmidt
|
November 3, 2015 at 8:15 am
Timezone Zurich wa from the beginning, even before I installed EE4.
Date format: j. F Y
Time format: G:i
Everything was o.k. before daylight saving time changed.
Events that were created before und also after daylight saving time changed, show the same effect as you can see online. calendar add-on and lsit o.k.
Single event and upcoming events +1h
From WP general settings after Zürich:
UTC-Zeit ist 03.11.2015 15:08:18
Deine lokale Zeit ist 03.11.2015 16:08:18
Diese Zeitzone ist zurzeit in der Winterzeit.
Die Sommerzeit beginnt am: 27. März 2016 1:00.
|
|
Lorenzo Orlando Caum
|
November 3, 2015 at 9:59 am
Hi Joachim,
We are having trouble reproducing this issue. Could you let us know if the date times in your event editor appear with the correct time?
What happens if you re-save an existing event and then check the single event page?
—
Lorenzo
|
|
Joachim Schmidt
|
November 3, 2015 at 10:24 am
Wordpress Backend List of events – time +1h i.e. 20:00. Edit event right time 7pm – 10pm. Re-saved – still wrong (+1h) in single view and upcoming events widget. Right time in calendar add-on und list table, as you can check via links in the first post.
|
|
Joachim Schmidt
|
November 5, 2015 at 3:35 am
O.K. I found that when I am using the Tribulant Newsletter plugin these EE4 core shows +1h. If deactivate Tribulant Newsletter everything is o.k. with EE4.
I will post in their support forum. What else can I do?
|
|
Tony
|
November 5, 2015 at 5:12 am
Hi there,
I had a look at that plugin and can see it is using date_default_timezone_set() which is what is causing the problem.
WordPress expects the default timezone to always be UTC, once you change that, strange things start happening to anything that uses Dates, as EE is heavily reliant on date working correctly it shows up more, but the cause is the use of that function.
A couple of examples explain this can be found here:
https://weston.ruter.net/2013/04/02/do-not-change-the-default-timezone-from-utc-in-wordpress/
https://vip.wordpress.com/documentation/vip-development-tips-tricks/use-current_time-not-date_default_timezone_set/
Unfortunately there is no quick fix, if may be possible to just comment out that code from the plugin until the author can add a proper fix, although you will need to check with them if this would work.
|
