Last week I was involved in a risky, adrenaline-pumping endeavor, one that definitely raised my standing heart rate. Carefully mapping out each step of the process, I thought I had ensured what executions were needed in order to survive the ordeal with at least everything I began with…my website was at stake. I had decided to upgrade, but still left out one important action: research the side effects.

The blog portion of my website is powered by WordPress. My version (2.3) was working fine, but I had heard that the newest version (2.6) had some very nice additions, mostly behind-the-scenes tweaks and extras of which I will avoid boring you. Somehow I decided that an upgrade was appropriate and began the uploading of hundreds of new files and folders, deleting or renaming others, and changing certain lines of relevant code. As this post is proof that I successfully made the upgrade (simply because it is visible to you), there was still one glitch that resulted (and I suppose I can be very thankful it was only one problem…aside from a few of the plugins that don’t work with this version). Somewhere, in the deep bowels of the thousands and thousands of lines of code, there were a couple words of coding gibberish that failed to translate with one of my databases on the server that needs to intimately communicate with this new upgrade. This coding hiccup means that the categories that I usually assign to each post (sort of like subject tags based on each post’s content) does NOT appear. So if you are accustomed to searching for previous posts in any of my category topics…I’m sorry. I’m working with my web host to find a certain missing file that would have existed prior to my upgrade. Until I get this fixed, you will have see “Filed under , ,” at the bottom each post, where it normally would list the categories under which that post should fall.

Ironically, three days after I installed the 2.6 version upgrade, version 2.6.1 was released that fixed 60 bugs, including this very one!! I suppose this was inevitable as I am not a prognosticator.

Popularity: 6% [?]