SimpleCalendar

Hello @toulip

Sorry that you are encountering this issue here. Interested to see if anyone else is facing this issue as well. We at our demos have never had to re-authenticate.

Our Google app is also in test mode, so that does not matter.

Hey @pamjasperx –

Sounds like that issue may be related to the 3.2.21 version of the plugin. If you upgrade to 3.2.22 you shouldn’t see any fatal errors on the site. If you run into any issues let me know what kind of error you see in the logs.

Hey @funex –

Can you share the function involved in wp-content/themes/canary/inc/filters.php on line 109? It looks like that may have something to do with the error. Could you also let us know what version of PHP your server is running?

Hey @norikod1

Do you have FTP access to the site? If so, you could rename the plugin under wp-content/plugins/google-calendar-events to something else (like google-calendar-events2). That should disable the plugin which would prevent any errors that may be output from it.

Hey all-

For now we removed the 3.1.21 version of the plugin and released 3.1.22 which contains the 3.1.20 code. This should allow users to auto update to the version without any issues as well as prevent anybody from downloading the version with the fatal error. Let me know if you have any issues getting the plugin activated again.

We’ll be updating our testing and QA process to ensure that an issue like this doesn’t make it’s way to our users again. Sorry about this issue — thank you for being a user and supporting Simple Calendar!

Hey all-

For now we removed the 3.1.21 version of the plugin and released 3.1.22 which contains the 3.1.20 code. This should allow users to auto update to the version without any issues as well as prevent anybody from downloading the version with the fatal error. Let me know if you have any issues getting the plugin activated again.

We’ll be updating our testing and QA process to ensure that an issue like this doesn’t make it’s way to our users again. Sorry about this issue — thank you for being a user and supporting Simple Calendar!

Hey all-

For now we removed the 3.1.21 version of the plugin and released 3.1.22 which contains the 3.1.20 code. This should allow users to auto update to the version without any issues as well as prevent anybody from downloading the version with the fatal error. Let me know if you have any issues getting the plugin activated again.

We’ll be updating our testing and QA process to ensure that an issue like this doesn’t make it’s way to our users again. Sorry about this issue — thank you for being a user and supporting Simple Calendar!

Hey all-

For now we removed the 3.1.21 version of the plugin and released 3.1.22 which contains the 3.1.20 code. This should allow users to auto update to the version without any issues as well as prevent anybody from downloading the version with the fatal error. Let me know if you have any issues getting the plugin activated again.

We’ll be updating our testing and QA process to ensure that an issue like this doesn’t make it’s way to our users again. Sorry about this issue — thank you for being a user and supporting Simple Calendar!

Hey all-

For now we removed the 3.1.21 version of the plugin and released 3.1.22 which contains the 3.1.20 code. This should allow users to auto update to the version without any issues as well as prevent anybody from downloading the version with the fatal error. Let me know if you have any issues getting the plugin activated again.

We’ll be updating our testing and QA process to ensure that an issue like this doesn’t make it’s way to our users again. Sorry about this issue — thank you for being a user and supporting Simple Calendar!

Hello,

Thanks for reaching out! We recently released custom PHP formatting allowing 24-hour event time display in a new release of FullCalendar 1.0.8, can you update to this and let me know at [email protected] if you have trouble?

Best regards,
Joshua Harris
Simple Calendar Support