I was challenged today by the thoroughly flawed WordPress 2.3 upgrade process. For those who do not know, WordPress is a personal blogging platform/CMS that powers this site and millions worldwide. Generally, I am extremely satisfied with Matt Mullengweg’s product, and somewhat pleased with how he treats his customers. This morning’s surprise, was a horse of a different color.

For security purposes and potential flexibility, I upgraded from 2.23 to 2.3. This process should have only involved deleting the previous php files and upping the new ones. Key phrase here… should have. Murphy’s Law kicked in and put me through a test of skill and mental toughness, which tested my self-management skills.

Now, in situations like these frustration can rise to the surface and blood can begin to boil. That being said, it never helps the situation. Keeping my cool, I documented each error/issue, and strolled over to the WordPress support forums to confirm what I believed to be the cause of my site’s schema-related illness.

After some coding, FTP use, and plug-in deletion, I had accomplished a successful upgrade to WordPress 2.3 from 2.23 within a manageable amount of time. Lesson here was to self-regulate for positive results when faced with an unexpected batch of problems.

Share This