Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter Zzzptm

    (@zzzptm)

    Wow… I got the correct credentials entered (after I found the email from my host in which he mentions the new server name…), the install.php connected fine to the database, gave me a button to log in and…

    500 – Internal server error.
    There is a problem with the resource you are looking for, and it cannot be displayed.

    If I connect it to my daughter’s 3.4.1 database, I can run the admin panel, but the blog itself shows up blank. When I connect it to my 3.5 database… the one with all my STUFF in it, I get the error 500.

    It connects to my database. No action…

    After I DELETE, not rename, DELETE all the plugins and themes except akismet and twentytwelve, I get a login for the admin panel, the blog is still blank.

    Admin panel says “ERROR: The themes directory is either empty or doesn’t exist. Please check your installation.” Yeah, I know about that… suppose I should fix that…

    I activate the twentytwelve theme. YAY! My blog appears!

    So I had to DELETE all my plugins and themes, not just rename them. DELETE.

    This is broken behavior, if you ask me. If there’s some kind of problem with a plugin or theme, it should have a graceful fail to where the plugin is deactivated or the theme deprecates to a default that works. Getting an Error 500 that persists until I delete files is a bad situation.

    I go to update akismet and… guess what…
    500 – Internal server error.
    There is a problem with the resource you are looking for, and it cannot be displayed.

    Noooooooooooooooooooooooooooo! That’s part of my antispam arsenal! This needs fixin’, and fast!

    Thread Starter Zzzptm

    (@zzzptm)

    Did the manual update and I’m at the “Error establishing a database connection” screen. Time to edit the proper file and see if I get that 500 again… have to say, though, it’s a pleasure getting a different error. Indicates progress. 🙂

    Thread Starter Zzzptm

    (@zzzptm)

    Renaming plugins and themes did not bring it back.

    Time to try the manual upgrade.

    Thread Starter Zzzptm

    (@zzzptm)

    I don’t think I have logging enabled… and I don’t know how to enable logging from my site control panel. I’m not local to my server.

    Thread Starter Zzzptm

    (@zzzptm)

    Did not work… I’ll give a shot at a manual upgrade to 3.5. I’ll let you know how that goes.

    Thread Starter Zzzptm

    (@zzzptm)

    The first was mentioned in another thread with a discussion of getting an error 500 immediately after a 3.5 upgrade as having worked.

    The second was a troubleshooting step in the “disable all plugins” instructions given in the main thread from the admins about 3.5 issues.

    As for IIS and servers, everything worked fine with 3.4.1 and continues to work fine on my daughter’s 3.4.1 blog on the same website. I’ve had my wordpress blog there for years and it’s worked just fine.

    This is why I’d like to know if I can roll back to 3.4.1, which is my “last known good” set of files on the server, or if 3.5 makes any database changes that aren’t backward-compatible.

    Since this one is marked “resolved”, perhaps the WP support folks are ignoring it. I’ll see if there’s another active thread or start my own…

    I added the .htaccess file and the line of code in wp-settings.php. Still no go.

    My daughter’s blog on 3.4.1 is running fine on the same server my 3.5 upgrade is giving an error 500.

    Can I roll my blog back to 3.4.1, or will that throw errors on a 3.5 version of the database?

    My blog: zzzptm.com

Viewing 8 replies - 1 through 8 (of 8 total)