Fatal error on upgrade from 4.0.0 to 4.0.3

  • Resolved Broome Arts

    (@broome-arts)


    9 years ago

    Got this error, and I’m blocked from all administrative actions too!

    The server encountered an internal error or misconfiguration and was unable to complete your request.
    Please contact the server administrator, cgiadmin@yourhostingaccount.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
    More information about this error may be available in the server error log.
    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

    Am manually restoring from backup, is there a list of files that were changed from 4.0.0 to 4.0.3?

    https://wordpress.org/plugins/the-events-calendar-category-colors/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Andy Fragen

    (@afragen)

    9 years ago

    I have no idea how or where that error came from, nor do I have any idea why you have been locked out. You will definitely have to take this up with your host. From 4.0.0 to 4.0.3 the only substantive change was in the PHP version check and error message.

    You must be running PHP 5.3 or greater to continue using this plugin.

    The CHANGELOG should tell you everything that’s changed and if you look e plugin up on GitHub you can see exactly what the changes have been.

    Sorry and I hope you get this solved but you will need your hosting provider’s support.

    Thread Starter Broome Arts

    (@broome-arts)

    9 years ago

    Thanks, Andy. My host appears to be running PHP 5.3. I’ve gotten in contact with their tech support, and they’re blaming the custom theme I’ve been using for the last two years.

    Coincidence isn’t causation, but I wanted to rule as much out as I could.

    Thanks for your lovely plug-in, it gave me a simple (and visually pleasing) solution to what was going to be a knotty problem!

    http://www.broomearts.org (when it’s eventually working)

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal error on upgrade from 4.0.0 to 4.0.3’ is closed to new replies.