• My WordPress automatically updated to 4.6.1 last night.

    Now it’s broke.

    I get an HTTP 500 error when I try to access the wp-admin.

    I’m reading all this junk about phpmyadmin and am having an awful time just trying to figure out how to install the darn thing and look at it. I’m not a techie, and UX clearly isn’t a strong point amongst the techie community. Apparently I’m supposed to put the zip file in my root folder? I don’t see a htdocs in my C drive. I just have no clue.

    Just very frustrating to have a website that was working fine yesterday to not be working today, the fixes beyond my technical know-how, and now spending hours just trying to fix my website instead of generating content that I am already badly behind on. That is the point of WordPress, no – a highly customizable and user friendly CMS for the non-technical?

    MY website is http://www.HoodHomesBlog.com.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator t-p

    (@t-p)

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter baronguard

    (@baronguard)

    I appreciate the response, however that is copy-paste of everything I’ve already read.

    And it probably will work – I am still just trying to figure out how to get to phpmyadmin dashboard. If I can do that and then figure out how to turn off plugins – great.

    So far I’ve been unsuccessful and clearly just need to hire someone to do this $%@#.

    Wordpress was awesome because I was able to build a web site with little technical knowledge – just some simple HTML tags. No more, it seems.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WordPress updated to 4.6.1, now broken’ is closed to new replies.