|
Mike
|
December 3, 2018 at 4:50 pm
Activating EE3 changes the local time as displayed on the WP Setting – General tab. For example, without EE3 activated:
Timezone Chicago
Choose either a city in the same timezone as you or a UTC timezone offset.
Universal time (UTC) is 2018-12-03 23:35:07. Local time is 2018-12-03 17:35:07.
With EE3 activated:
Timezone Chicago
Choose either a city in the same timezone as you or a UTC timezone offset.
Universal time (UTC) is 2018-12-03 17:50:52. Local time is 2018-12-03 11:50:52.
|
|
Josh
|
December 4, 2018 at 8:30 am
Hi,
Thanks for reporting this. There’s a branch of EE3 that fixes this issue, and you can download it here.
Please do let us know if installing the branch fixes the issue for you.
|
|
Mike
|
December 4, 2018 at 2:27 pm
Josh,
Thanks for the info and link on the alternate branch. My concern would be we’re using the following versions of EE3 and add-ons:
EE3 – v3.1.37.14.P
EE-Calendar – v2.2.7P
EE-Members Addon – v1.9.8.p
EE-Multi Event Registration – v1.0.5.p
EE-API Plugin – V2.1.4.P
The version on the branch appears to be 3.1.30, based on the included readme.txt. If that’s true, this version is almost 6 years old! What are we giving up or incompatibilities may crop up.
|
|
Josh
|
December 4, 2018 at 2:36 pm
The readme.txt is wrong. If you check your site’s copy of readme.txt, it probably also says 3.1.30. The version number of the branch I sent you is 3.1.37.15.p. It’s one version ahead of your site’s.
|
|
Mike
|
December 4, 2018 at 3:14 pm
OK, I’ve installed the alternate branch in our staging environment and it does appear to have fixed the local time/timezone issue. FYI, this also fixed an issue with another plugin that I suspected was related to the change in local time. I’ll do some more testing in the staging environment to confirm all is well and then install it in production. Thanks.
|
