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

  • Resolved Wendy


    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:
    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:
    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:
    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:
Viewing 15 replies - 31 through 45 (of 71 total)
  • @mgc I highly recommend you completely delete the files for the plugin first and then re-upload via (S)FTP (what’s what I did [and others] which then resolved the issue) to confirm everything’s there that should be & nothing is there that shouldn’t.

    @dangarion has completed downloading for me 100% of the time (earlier today and just now a couple of times.)

    Technically, this plugin currently has 14,144 files (13,999 of them are from the vendors/libraries being used with google/apiclient-services being 12,336 files all on its own.) I do think that is probably more than what’s really needed and this bloat could be causing extraction issues on certain hosting setups.

    Since Google’s apiclient-services is causing a bunch of the bloat, I looked into it and saw there’s every possible API (it seems) being included. Why would we need ad-related, Analytics, YouTube, and more included in the files for this plugin? Any way these can be slimmed down to only what’s needed within the vendor files?

    I’m thinking slimming Google’s apiclient-services down to only what’s needed would alleviate the issue(s) being experienced here (also improve the experience for people overall.)

    As such, @simplecalendarsupport, you probably want to consider following the “Cleaning up unused services” section at to exclude unused API services as Google themselves recommend (since it really is undue bloat to just include everything [again, likely causing the issue here]) & made sure to provide an avenue to do so (thankfully without too much trouble, it seems πŸ™‚).

    syntax error, unexpected ‘|’, expecting variable (T_VARIABLE)

    I hope there will be a fix issued soon.

    I am getting the same message as @cosaco. This is what I am getting in my admin email. I know this site is downlevel for PHP and I am working on getting them moved to better hosting to fix that.

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.5.1
    Current theme: child-ifeature (version )
    Current plugin: Simple Calendar (version 3.1.32)
    PHP version 5.6.40

    Error Details
    An error of type E_PARSE was caused in line 526 of the file /home/bcogwebmaster/public_html/wp-content/plugins/google-calendar-events/vendor/nesbot/carbon/src/Carbon/CarbonInterface.php. Error message: syntax error, unexpected ‘const’ (T_CONST), expecting variable (T_VARIABLE)

    Just wanted to post another update. It probably doesn’t matter on Linux systems but I downloaded the zip file to my Windows system to see what all was in it as the size of the plugin has increased from around 3 MB to around 15. Several of the files as I was trying to extract it have file names that are way too large for Windows to use. I had to quit the extraction as I consistently had to click skip.


    I was having this same issue. My site is hosted on and I noticed that I was still running with PHP 7.0.29. So I went into the cPanel and used the PHP Selector to upgrade to 7.2 which gave me 7.2.26. After doing that I was able to re-install the Simple Calendar plugin and it worked again.

    I hope this helps someone out there!

    Hi – Thank you so much, all, for the guidance and tips. We deleted the plugin from the admin side, and uploaded the newest version by FTP. We’re back to good.
    Thank you again!

    Good to know some of you can address the plugin’s shortcomings for yourselves. For the rest of us, will there be a patch update issued by the developer?

    @mgc I’m sure they will issue a fix soon. The developer is aware of the issue.


    Thanks, @dljordaneku! Fingers crossed here. Cheers! πŸ™‚

    I tried uploading the zip file of the latest build and unzip it in the plugin directory and it didn’t work. I still get that the website is down. So I hope the developer puts out a fix soon or I will have to use another plugin.


    I have the same error after upgrading. It looks to me the developer is using code which can only run in php7.1. Is there any way to download the earlier version so that we can revert? Thanks.

    Found earlier versions of the plugin here

    Scroll down to the bottom, you will see a dropdown where you can select the version you need to download.

    I reverted the plugin to the earlier version and my site is back to working.

    Can you please tell me: in which folder are my “personal” configuration data. When I install it knew, I don’t whant to configure it completely again. Is it the iclude folder?
    And can I just copy it into the new installation??
    Bets wishes

    @kaoe Settings for plugins are almost always saved to the database (not actually web files at all) with some specific cases where they’re implemented via a wp-content/uploads/ folder.

    Having direct PHP file access or files needing to be modified within the plugin folder is highly discouraged (if not outright blocked from being allowed from the plugin submission review process.) How could people update a plugin to a new version if it overwrites their settings in the process due to them being part of the plugins main files? They couldn’t; hence why they’re stored via the database and/or wp-content/uploads/ folder(s).

    As such, you should be fine to delete the files and re-upload the complete plugin via (S)FTP.

    This (fully delete the plugin files and fully re-upload via [S]FTP) still seems to be the current resolution to this problem as the only people reporting they’re still having issues are ones that haven’t said they tried this method or otherwise have their own separate problems preventing them from doing so.

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