HTTP 500 error after upgrade to 3.8

  • Resolved loiswakeman

    (@loiswakeman)


    10 years, 3 months ago

    I have just updated a site to from 3.7.1 to 3.8. Running on IIS7.5, about which I can do nothing, so “switch to Linux” isn’t an answer I can use!

    The auto-install failed, so I deleted wp-admin and wp-includes and maint, temporarily renamed the plugins folder, uploaded the WP files from the downloaded ZIP file, including the root files.

    The site is in a sub-directory (wordpress) but intended to run from the root, so I made sure I still had the edited version of root/index.php including the directory:

    require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' );

    and now I get a 500 error for the site and the backend. (There’s no point in giving you the URL as I have temporarily reinstated a skeleton HTML site till I get this fixed.)

    I still have the wp-config.php and web.config that were working before the update.

    Before I try to get server logs from support, can anyone spot anything I have done obviously wrong please? This is the first time in about 50 updates that things have gone wrong, and I am floundering a bit 🙁

Viewing 2 replies - 1 through 2 (of 2 total)
  • harmonyinfotech

    (@harmonyinfotech)

    10 years, 3 months ago

    Going through the logs would be easiest to figure out the problem. Could be file permissions issue.

    Thread Starter loiswakeman

    (@loiswakeman)

    10 years, 3 months ago

    In case anyone else finds this helpful, this was entirely due to a faulty (interrupted) FTP upload which meant that a file was missing from the core – I had done a file comparison but must have missed that one.

    When I turned on debugging, I could trace the name of the missing file in the error message, instead of seeing the white screen, and once that was uploaded, I was fixed.

    This page also has some useful info that might help others (including how to debug).

    Happy new year.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘HTTP 500 error after upgrade to 3.8’ is closed to new replies.