zenrender

Hi Chris, sorry to hear this is happening to you, but don’t lose hope! Once I figured it out, it was quick to correct.

When you first set up your WordPress installation, there was a point when you had file access to your web site, and there wasn’t a blog on there yet, and the program looked similar to a Mac Finder or Windows File Explorer. You had to copy a folder of files up to your server that would later become your WordPress installation. If your WordPress install is doing what mine did (blank white screen after upgrade to 3.6), you’ll need to be able to see that FTP/FileManager view again to fix it.

For that you’ll need an FTP (File Transfer Program). There are many free ones, but I suggest FileZilla Client (free for Windows and Mac)

Your website might also have “CPanel” access, which is usually available by going to www.{yourwebsite}.com/cpanel or possibly cpanel.{yourwebsite}.com From there, you can usually get some sort of file manager access.

You’ll need a username and password for the CPanel or FTP access, that will *probably* be different from your WordPress login user/pass, but *might* be the same as your email login for the first account of the Domain, when it was created.

Just checked your https://www.lawlerfirmllc.com site though, and your blogs are coming up just fine. Hope that means you figured it out.

Answered my own question:

Looks like one of my plugins, namely WordPress Automatic Update was causing problems for any of the WordPress installations that had it. At least that was the one that wouldn’t re-enable when I did the following:

1. FTP into your site, and find the wp-content folder
2. In that folder, *rename* the plugins folder to plugins.old
3. Log into your dashboard as usual, and check the Plugins area.
4. You’ll notice everything’s been disabled, that’s fine.
5. In the FTP again, rename the plugins.old back to plugins.
6. In the plugins dashboard, re-enable the plugins again (bulk action is fine).
7. Make note of any of the plugins that won’t activate, and enable the rest.
8. See if there’s an update for any of the plugins that won’t update.
9. Decide whether or not you *really* need the plugins that don’t work.