I build blogs for a living, so I feel confident in saying that I am pretty knowledgeable when it comes to WordPress. But, the day I upgraded to WordPress 3.0, I felt clueless.
I was building my latest blog when I saw the notice in the WP dashboard to upgrade to WordPress 3.0, so I clicked, upgraded, and continued working.
I was placing a video in the sidebar of the blog, and I remember this explicitly, when I went to refresh the page, the video was there, but it was the wrong size.
So, I went back to the dashboard, input the correct dimensions for the video, and went back to refresh the page. Nothing changed. The video was still too big.
After about an hour of troubleshooting, I was frustrated beyond belief! I was ready to throw my computer through the window. Nothing like this had ever happened to me before and I had no idea how to fix it.
You see, I was able to add new things to the blog, graphics, links, etc, but I was unable to make any changes. It was infuriating!
I finally logged into the live chat at my web host, which is always my last resort. I had two techs try to figure this out, and they could not. Again, I cannot describe the level of frustration I felt. So much that I actually abandoned the blog for three days. I was that stumped!
To keep from making a long story even longer, let me tell you what I eventually found out. The culprit was a new plugin that I had not added to the blog, but apparently had been added automatically when I upgraded to WordPress 3.0. It’s called WP Super Cache and I hate it!
I don’t have any idea what the plugin was created for or what it’s used for and to be honest, I couldn’t care less. All I know is that this demonic plugin was somehow preventing my blog from showing me the updated pages when I refreshed. If you want, you can read about the plugin here (but I wouldn’t advise it).
Now, the first thing I do when beginning a new blog, before I do anything else, is go in and delete that awful, hateful plugin.
My hope is that this post will either help you if you’ve been having the same problem, or save you the agony I went through with it.
My fantasy is that someone from WordPress will see this post and realize what a royal screw up it was to force WP Super Cache on unsuspecting WordPress 3.0 users.
