It looks like I’ve finally fixed the Home page issues here.
Back in March, my blog started acting weird. I’d post something new and it wouldn’t show up on the Home page for everyone. It showed up for me, though. At least sometimes.
Then I started having issues with the permalinks. You see, WordPress (the blogging platform I use) stores all of its content in a database. Blog pages don’t exist as regular HTML pages like a regular Website. They’re generated on the fly as needed. The permalink is a formulated URL that brings up a specific blog post or other content. For some reason, my permalinks insisted on including a double slash (//) after the domain name. When I tried to restore them to my preferred format (www.aneclecticmind.com/year/month/day/post-name), my blog would cease working.
This was driving me nuts because I couldn’t figure it out for myself and because I was traveling extensively and simply couldn’t take the time to troubleshoot it with my hosting company. When I got home from traveling, I tried once or twice to get it resolved and failed.
I tried again when I was in Ketchikan last week with my laptop and a few hours to spare. My ISP, Bluehost, escalated it up to Tier 3d. Someone did something and they fixed the permalink issue — although they did set it incorrectly. I corrected it today and it “stuck” without causing the whole blog to come crashing down.
But the Home page refresh issue continued to rear its ugly head. I posted two blog posts earlier today — one as a test and the other to get some half-finished content online. Two individual people contacted me to tell me that the post appeared at the link provided on Twitter but not the Home page. I checked and found the same thing.
I logged in to make sure the posts hadn’t been somehow deleted. They were there. I went to the Home page and they appeared. As they should.
I logged out and checked again. They were gone. The most recent post that appeared was the one I’d written back on March 8.
What the hell?
I called Bluehost to set up another ticket. It took a few tries for the support guy to duplicate the problem. He was certain it was related to caching.
I used to use a caching app to speed up the site. The tech support folks had told me that it might be causing the Permalink issue so I deleted it.
The Bluehost guy couldn’t fix this issue, but he promised to open a ticket and move it up to Tier 2. I thanked him and hung up.
I was unhappy. I like to blog. I’ve been blogging here since 2003 — 16 years in October. There were a lot of things I wanted to say, a lot of stories I wanted to share about my recent travels. I can’t add new content to my blog if my blog isn’t working right.
So I rolled up my sleeve and started poking around in the WordPress files that aren’t in the database. I found a cache folder. Inside the cache folder was a folder named all. That folder was full of numbered folders, including some that corresponded to years and, within them, months. Just like WordPress organizes my post permalinks. There was also an index.html file. I opened it up and guess what I found? The home page that kept appearing for people who weren’t logged in.
I called Bluehost tech support again. Of course, I couldn’t talk to the same guy. The guy I got wasn’t quite as knowledgeable. I told him about the problem and what I’d found. I asked him if he thought I could delete the all folder. He didn’t think that would be a good idea. How about renaming it? Sure. I could always restore the name.
So I renamed all to _all. And I went back to the Home page of my blog. And it properly displayed my most recent post at the top of the Home page.
I asked him to look at it. It showed him the same thing.
I got on Twitter and asked my followers to try it and report back. A handful of them did. It was working right for them, too.
Problem solved.
I deleted the _all folder and everything still works fine. Then I reinstalled a highly recommended cache plugin and turned it on. Still fine.
So at this point, my blog seems to be mostly fixed.
I say mostly because I need to update WordPress to the most recent version and I can’t because the whole blog is running on an old version of PHP and I can’t seem to update it. That already has a Bluehost ticket in Tier 2 going.
Why can’t things be simple?