Have you try disabling the plugins ?
Yesterday I saw all of these messages on the Word Press sites about updates to both plug-ins and updating to 3.9 so I did both at the same time. However, I can’t get into the backend to disable the plugins or even test them out.
This is the message I get when I try to log in to the back end of one of the sites:
http://usagain-atlanta.com/wp-login.php
“Oops! Google Chrome could not connect to usagain-atlanta.com”
And I believe it has to be connected to the updates because the one site that I didn’t add any updates to works just fine. I can see the main site and I can log into the backend of the site.
I even tried seeing if it was a matter of the computer. I tried Google Chrome and Safari, but I get the same error messages on both.
I tried logging into my main site to see if this would fix the issue, and the one site that I did not make any updates on works just fine so I know the issue is Word Press 3.9 updates or one of the plug-in updates.
I did notice that when I log into the main site and try to click on “Manage” to get into the backend of the Atlanta site, I get this message “Drat! It looks like you are running an old version of Jetpack on USAgain Atlanta, please (upgrade) in order to access the latest features!”
Any ideas of what I should do there? I tried removing the “jetpack” folder out of “plug-ins” on my FTP site to see if that would do anything, but I still can’t log in. And I’ve tried going to my FTP site and changing “plugins” to “plugins.hold,” but I still am having no luck.
I really wish I’d have never made any updates and just stuck to the older version.
I tried resetting the plug-ins folder and nothing changed. I still couldn’t log in. But after stepping back to breathe and try to figure out what to do next, I went home and used my PC. I realized none of the problems I was having on a Mac were ones I was having on a PC. Now whether that’s coincidental or not, I went to the same live site and the same backend of the site, and now I can see everything.
Not sure if the faulty plug-ins are linked to a browser or PC vs. Mac issue somehow. But I tested them all in Firefox on a PC, and I don’t have any of the issues I had all day today.
I’d suggest users try this first before renaming everything, etc.
