Support » Plugin: Simple Calendar - Google Calendar Plugin » Critical site error after update

  • Resolved Wendy

    (@craew)


    After an update to version 3.1.32 the website return a critical error for this plugin. I currently disabled the plugin.

    Got error 'PHP message: PHP Parse error:  syntax error, unexpected '|', expecting variable (T_VARIABLE) in /home/xxxx/apps/default/wp-content/plugins/google-calendar-events/vendor/nesbot/carbon/src/Carbon/Traits/Date.php on line 1032\n', referer: https://xxxx.be/wp-admin/
    
    Got error 'PHP message: PHP Parse error:  syntax error, unexpected '|', expecting variable (T_VARIABLE) in /home/xxxx/apps/default/wp-content/plugins/google-calendar-events/vendor/nesbot/carbon/src/Carbon/Traits/Date.php on line 1032\n', referer: https://xxxx.be/wp-admin/
    
    Got error 'PHP message: PHP Parse error:  syntax error, unexpected '|', expecting variable (T_VARIABLE) in /home/xxxx/apps/default/wp-content/plugins/google-calendar-events/vendor/nesbot/carbon/src/Carbon/Traits/Date.php on line 1032\n', referer: http://xxxx.be
    
    Got error 'PHP message: PHP Parse error:  syntax error, unexpected '|', expecting variable (T_VARIABLE) in /home/xxxx/apps/default/wp-content/plugins/google-calendar-events/vendor/nesbot/carbon/src/Carbon/Traits/Date.php on line 1032\n', referer: https://xxxx.be/wp-admin/network/site-info.php?id=6
Viewing 11 replies - 61 through 71 (of 71 total)
  • caionog

    (@caionog)

    I already updated to php 7.4, also tried to reinstall plugin trough FTP but no success…

    Awaiting for a solution…
    Thanks!

    pbwpwork

    (@pbwpwork)

    Like others have pointed out, I don’t know why this has been marked as resolved when it really isn’t properly…. I have solved the problem by rolling back the plugin from 31.1.32 to 31.1.31. As when I ran .32 with PHP 7.3.18 (WordPress 5.5.1) it crashed the whole site. However I would love to be running the latest version as I don’t know if I am opening my website up to any security flaws by using an older version.

    @simplecalendarsupport is the problem going to be fixed, with a future update?

    KZeni

    (@kzeni)

    @caionog It’s always helpful to provide the WP_DEBUG details for the error when there’s something like this. In this case, there’s been a number of different errors different people have encountered so yours might be a unique case that definitely shouldn’t be overlooked, and providing those details for the developer to have proactively can definitely help guarantee the issue is resolved for you sooner than later.

    mgc

    (@mgc)

    Still no official fix update?

    simplecalendarsupport

    (@simplecalendarsupport)

    Hey everyone,

    We just pushed out 3.1.33 today. It should address a lot of the issues that have been going on. The plugin was extremely bloated and for some users causing issues installing. We have trimmed things down a lot. You will need to make sure you are running PHP 7.3+ now as well.

    Thanks for your patience while we worked through this!

    This version still takes long to update but it works. Thank you, @simplecalendarsupport!

    simplecalendarsupport

    (@simplecalendarsupport)

    Thanks for the confirmation @mgc

    It should be better going forward as we have reduced the plugin files by A LOT. So the slowness this time was probably just because it needed to clear out some of the old files.

    Have a good one!

    So just to verify that if running php 5.x its still not going to work.

    Darrell

    simplecalendarsupport

    (@simplecalendarsupport)

    That is correct. We updated a lot of the vendor packages to help bring things more up to date. So now you will need at least PHP 7.3 in order to run the plugin.

    @simplecalendarsupport

    Please take a look to the issue related GuzzleHttp you have updated on the plugin.

    It conflicts with several other plugins from other vendors thas are needed for us.

    I offer you help on trying to solve this issue if you like / want.

    Kind regards

    Inaki

    danielrufde

    (@danielrufde)

    See https://wordpress.org/support/topic/update-to-3-1-33-broke-my-site/page/2/#post-13515406 regarding the unscoped dependencies / vendor folders.

Viewing 11 replies - 61 through 71 (of 71 total)
  • The topic ‘Critical site error after update’ is closed to new replies.