Well, the problem is FINALLY resolved. NONE of the suggestions were correct. Come to find out, when WordPress switched over to the new 3.7.1 version, it messed up a lot of people. They then did something to fix their problems, but those who did NOT have that problem, NOW had one. (Make sense?) So now they have fixed the SECONDARY problem. WordPress and GoDaddy BOTH were involved in the problem. (It’s more complicated than I’m probably even allowed to say, but BOTH companies were at fault.)
But bottom line is…PROB NOW FIXED.
I do hope they all learned from their mistakes, though, and next time there are updates, they are more careful to test them BEFORE launching them onto the public and save a TON of grief and heartache.
I do thank those who helped so very much, though. Thanks for caring and trying. Your efforts were much appreciated.
Glad to hear it’s been sorted.
It’s more complicated than I’m probably even allowed to say,
Not sure what you aren’t allowed to say, but FWIW, many people updated WP to 3.7 and 3.7.1 without any problems whatsoever.
WP is always widely tested but it also depends on many people (volunteers) helping to test beta versions – it’s quite literally impossible to test on every possible server/site configuration.
We had been using the new version, 3.7.1, for over a month with no problem!
A LOT of people had trouble when they first switched. We were in the group that didn’t. So when they straightened out their first mistake, they created ANOTHER one. We were affected by that. So now they fixed their SECOND mistake. Too many mistakes if you ask me.
But it’s done now.
I’m curious to hear what the two problems were.
