Trouble after updating to version 3.2.18

Did you update from 3.2.17, or from an older version? The changes in 3.2.18 were quite small, so broader changes like this seem unlikely; but if your previous version was older, I’d need to know roughly what version you were previously on.

Hello Joe,

Thanks for your reply.

I updated from 3.1.18. The plugin had not been updated for well over a year.

I have now reverted the website to run 3.1.18.

The website works as it did before I updated to 3.2.18. That is, there are no issues when My Calendar version 3.1.18 is used.

I would appreciate your guidance on updating from 3.1.18 to 3.2.19.

Thanks,
Melissa

So, it turns out that there were some missing files in the 3.2.18 package. This might have been the cause of the problems you were having; I’ve shipped 3.2.19 to correct this. The only difference is that 3.2.19 isn’t missing files. Give it a try, and let me know if this resolves the issue.

That said, I’m on the verge of releasing version 3.3.0, due out around December 1st. This fixes a lot of issues, some which have existed throughout the 3.2 version, so you might actually be better off waiting for that.

Thanks for the reply. I went ahead and installed version 3.2.19.

The problems return with version 3.2.19.

1) The times of the events previously set at 9:00 am and 12:00 pm changed to 3:00 pm and 6:00 pm, respectively, as soon as I installed 3.2.19.

2) Likewise, when I tried to correct one of the events showing 6:00 pm to 12:00 pm, the correction did not stick. The system changed the time to 6:00 am and the date to 19th November 2021 – 20th November 2021 (instead of 19th November 2021).

Is there anything I can do to get this installation going before 3.3.0 comes out?

Thanks again!
Melissa

• This reply was modified 3 years ago by Melissa Davis. Reason: Added closing

That suggests that the timezone set in your MySQL database isn’t correct. Are you able to run a quick select query on your database? This query should give you the timezone offset your database is using:

SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);

Thanks for your reply. I am in the Chicago time zone. I ran the query on the website database.

The offset comes out as -7. Here is the result:

TIMEDIFF(NOW(), UTC_TIMESTAMP)
-07:00:00

Inside WordPress under settings > time zone, the dropdown, however, shows UTC+0.

Below this dropdown, the system shows Universal time (UTC) is 2021-11-18 20:09:25. Currently, Chicago time is 20:09:25. The WordPress system appears to equate Chicago time to UTC.

(Version 3.1.18 of the plugin was working right even with the above inconsistency. Version 3.2.19 does not appear to.)

Does this give any clue?

Thanks,
Melissa

Version 3.1.18 didn’t support timezones in any way; adding support for timezones required me to make changes so that My Calendar would know how the current time related to UTC.

So, the server is off; if you’re in CT, then that should come out as -05:00:00. Your WordPress timezone should also be set to the current time zone – Chicago is UTC-5.

I’d start with the simpler change – setting your WordPress timezone to the correct timezone, and see what you get then. However, I wouldn’t bet on that helping, since it seems like your server time is incorrect. The WordPress timezone shouldn’t be directly relevant for this.

Thanks for your reply and suggestion.

I switched the time zone setting inside WordPress, under settings > time zone, to UTC-6.

This change cut the number of events listed on the calendar from 6 to 5. The first event presently shown with at 3:00 pm, 17th November 2021 dropped from the display.

The times and dates of the remaining 5 events did not change.

The blue formatting currently applied to today’s event, i.e., the 6:00 am, 19th November 2021 – 20th November 2021 event, was lost when I switched the time zone to UTC-6.

BTW, the site is hosted at GoDaddy.

Where do we go from here?

Thanks,
Melissa

I suggest waiting until version 3.3.0 is released. One of the changes in version 3.3.0 is adding a filter to customize the database offset; this would allow you to get the right time output even though the database is misconfigured. Otherwise, your option is to communicate with GoDaddy support to check on the database timezone issue.

Sure, thanks for your reply. I look forward to version 3.3.0.

Best,
Melissa

Hi Joe,

Could you possibly give me a heads-up on when version 3.3.0 would be out?

Thanks,
Melissa

Barring something going wrong, tomorrow (Monday.)

Update is released; the filter in place to handle your situation is mc_filter_offset. You’d use it like so:

add_filter( 'mc_filter_offset', 'my_tz_offset' );
function my_tz_offset( $offset ) {
    return '-06:00:00';
}

Hello Joe,

Thanks a lot for sending this filter code snippet. I have a couple of questions in this regard.

1. Can I use this filter snippet with My Calendar version 3.1.18?

2. Do I put this line of code in functions.php?

Also, thank you for releasing version 3.3.0. I have PHP version 5.6 on my site. I have upgrade PHP to version 7.0 before using the latest version of My Calendar.

Thanks much!
Melissa

No, the filter was added in 3.3.0, and won’t do anything in earlier versions.

You could put this in functions.php, yes. It’s not the only option, but it certainly would work there!

I do highly recommend updating the version of PHP on your site; PHP 5.6 reached end of life on Dec. 31, 2018, and hasn’t received maintenance updates since then.