Rejoice!
On the other hand, what a ride.
When this problem began three days ago, I immediately called my hosting company (Bluehost), which has 24-hour support. That’s one of the things I like about Bluehost; you can actually speak to a real live person 24-hours a day, 7 days a week, and the hold time is usually very short. So far so good.
I told them it was probably some sort of cache problem on their end, but they initially denied it and insisted it was a code problem on my end and that I needed to hire a web developer to fix it. A search revealed that there are quite a few companies that offer themselves as troubleshooters for problems with WordPress blogs, and they charge varying fees for the service. But I couldn’t get any of these companies to get back to me. With one, for example, I kept opening tickets with questions, but I never heard a word back.
Meanwhile, I kept doing my own research as well as phoning Bluehost. This took an enormous amount of time, as you can imagine. I called Bluehost about seven times altogether, and talked for at least a half hour each time. But for those first five or so times (and this included each support person going to multiple supervisors for guidance) they insisted it was a code problem on my end, whereas I insisted it was a caching problem on their end. A frustrating standoff.
Well, to make a very long story shorter, some friends and bloggers kept telling me that it indeed was a cache problem, and they gave me enough details that I was finally able to convince the folks at Bluehost that it was a cache problem and that it was on their end. But now Bluehost was insisting (late last night) that I needed to upgrade to hosting on the cloud.
This morning I called again. This time I got a gentleman who said “Oh, I’ll clear the cache on our server.” And voila, problem solved…at least for now.
So I didn’t have to spend extra money getting someone to delve into my code and fix it. I didn’t have to upgrade and give Bluehost more money. Had I gotten someone knowledgeable there on the phone in the first place, I wouldn’t have had to spend three days working on this, nor would you have had to have the frustration (and fun?) of posting under identities other than your own when autofill decided to become a trickster. All of this was apparently due to a caching problem at the server, causing the cached versions to keep displaying rather than updating.
What did I learn from all of this? I learned that people can pay scads of money—up to $20,000 per month (and no, that’s not a typo)—for a dedicated server, if their traffic is high enough. I’ve learned that support staff don’t always have a clue what they’re doing (although I suppose I already knew that). I learned that these days we often get the semblance of support and competence—fancy advertising on websites, “tichets” that you open that promise immediate response but that are messages in a bottle that never reach shore—without the substance.
But most of all, at this moment I’m grateful that the problem seems to have been solved. I give a heartfelt thanks to that guy at Bluehost who knew what he was doing. And I hope the whole thing doesn’t happen again—but if it does, I know what a good provisional diagnosis would be, and I took notes so I can remember.
By the way, if there ever is a problem of a similar sort (and I hope there never is), I recommend that you either hit the CTRL + F5 keys simultaneously to see the latest version of the blog, or if that doesn’t work, add “?no-cache=1” (minus the quotation marks) after my blog URL neoneocon.com. You might want to note that down, as well as the address of my old blog if all else fails: http://neo-neocon.blogspot.com .
Boy, I hope this post shows up in a timely fashion. If not, it’s back to the drawing board.
