• Resolved IainPurdie

    (@iainpurdie)


    Our site just went down the with below message appearing regardless of whether you’re accessing the site or admin console:

    Warning: require(/var/www/vhosts/moshville.co.uk/Moshville/wordpress/wp-content/plugins/google-calendar-events/vendor/composer/../guzzlehttp/psr7/src/functions_include.php): failed to open stream: No such file or directory in /var/www/vhosts/moshville.co.uk/Moshville/wordpress/wp-content/plugins/google-calendar-events/vendor/composer/autoload_real.php on line 66
    
    Warning: require(/var/www/vhosts/moshville.co.uk/Moshville/wordpress/wp-content/plugins/google-calendar-events/vendor/composer/../guzzlehttp/psr7/src/functions_include.php): failed to open stream: No such file or directory in /var/www/vhosts/moshville.co.uk/Moshville/wordpress/wp-content/plugins/google-calendar-events/vendor/composer/autoload_real.php on line 66
    
    Fatal error: require(): Failed opening required '/var/www/vhosts/moshville.co.uk/Moshville/wordpress/wp-content/plugins/google-calendar-events/vendor/composer/../guzzlehttp/psr7/src/functions_include.php' (include_path='.:/opt/plesk/php/5.6/share/pear') in /var/www/vhosts/moshville.co.uk/Moshville/wordpress/wp-content/plugins/google-calendar-events/vendor/composer/autoload_real.php on line 66

    I checked this plug-in’s page when I spotted it named in the error, and spotted that it was updated “8 minutes ago”. I’ve no idea how to resolve this. I don’t have console access to out site’s server, and renaming the plug-in’s folder in an effort to prevent it functioning has done nothing.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Dear lainPurdie,

    we had the same problem.
    In order for you to acess dashboar of wordpress site, please rename your folder located in wp-content/plugins/google-calendar-events via ftp to “google-calendar-events_old”.

    Now you can access your WPress Dashboard.
    Let me know if this helped.

    Thread Starter IainPurdie

    (@iainpurdie)

    Will have a shot in a while. I’m backing the site up at the moment!

    I did try renaming the folder, but it didn’t help. Could be it was just cached and I needed a little more patience ??

    The updated plugin clashed with my homepage layout and the layout of another page where the plugin is used. The /wp-admin/ page responded with an error 500.

    I re-uploaded by FTP an older version I had on my PC and it’s back to normal.

    I have to say that I’ve stopped using what would have been the more useful function of this plugin a long time ago because it doesn’t work. At this time I am only using it to embed the grid calendar only.

    From this latest update I have no idea what exactly got changed and how but obviously it’s screwing up majorly.

    Hey all,

    There was a small window on Dec 28th, 2017 where Simple Calendar showed an update that wasn’t ready for release yet.

    Earlier today we released what should be the working & fixed version 3.1.11. If you download the latest release from https://www.ads-software.com/plugins/google-calendar-events/ it should work as expected.

    If for some reason, that download doesn’t work you can download the previous release (3.1.10) on www.ads-software.com at the direct zip link here: https://downloads.www.ads-software.com/plugin/google-calendar-events.3.1.10.zip

    Please let us know if you run into issues after downloading a fresh copy of 3.1.11.

    Thank you for helping to make Simple Calendar better by reporting bugs or issues you find!

    Hey all,

    I wanted to let you know that there was a hotfix released today (3.1.11.1) which should allow you to upgrade without the site crashing. If your PHP version is incompatible you should see a notice on the page explaining that and the plugin will deactivate itself.

    Please don’t hesitate to let me know if you run into issues- I’ll be monitoring these threads to help as much as possible.

    Regards,

    Zach

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘SIte down after update’ is closed to new replies.