• Resolved Puck

    (@puck)


    Upgraded today and instantly got a 500 error and the site became unresponsive.

    Moved the-event-calendar out of the plugins folder and was able to get back in to the back-end. Grabbed a fresh copy of the updated plugin and tried to reactivate and got this:

    Warning: require_once(/var/www/html/wp-content/plugins/the-events-calendar/public/template-tags/calendar.php): failed to open stream: No such file or directory in /var/www/html/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 164 Fatal error: require_once(): Failed opening required '/var/www/html/wp-content/plugins/the-events-calendar/public/template-tags/calendar.php' (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/html/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 164

    There is no “calendar.php” in the public/template-tags folder so this is a pretty glaring server-crashing bug.

    http://wordpress.org/extend/plugins/the-events-calendar/

    Update RESOLVED: poked around and found that that file shouldn’t even be called which reminded me I should clear my caches after the upgrade. Cleared my OPCode and nginx caches and was able to successfully re-activate the plugin.

    I’ll leave this here for anyone else having the same problem.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Looking into it, will get right back to you. =)

    Thread Starter Puck

    (@puck)

    Update RESOLVED: poked around and found that that file shouldn’t even be called which reminded me I should clear my caches after the upgrade. Cleared my OPCode and nginx caches and was able to successfully re-activate the plugin.

    I’ll leave this here for anyone else having the same problem.

    Phew. =)

    Thanks for confirming this for us, Puck – was indeed a momentary panic for the team when we saw this message 🙂

    Let us know if you need anything else here. And congratulations on posting the first 3.0-centric topic on this forum ever!

    Thread Starter Puck

    (@puck)

    I imagine you were freaking out as much as I was. After a switch from LAMP to nginx/php-fpm/FastCGI and using OPCode PHP caching I’ve had a few batches of weirdness because of all the caching going on (but a wickedly faster/leaner server).

    It didn’t spring to mind immediately because I was, as mentioned, freaking out. Glad it was an easy fix that I got to quickly. I think “clear your PHP cache” is probably going to become my “did you try turning it off and then on again?” whenever I have similar problems in the future.

    If you’re in Vancouver, BC in a few weeks, come on out to our live podcast! https://www.causticgear.com/event/caustic-soda-space-disasters-in-3d/

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘500 Error after update – missing file’ is closed to new replies.