Another Wordpress Blog

Like many bloggers, I’m in the process of upgrading their WordPress to the new version: WP 2.3. For many bloggers, upgrading will be a snap. Others will find their upgrade is technically just fine, but some plugins and widgets don’t work. Finding substitutes will take time.

So, it’s probably a good time to learn some tips for ensuring that you can maintain full functionality while you upgrade WordPress. I’ll include steps the WP developers don’t tell you!

1. Most plugins that deal with Categories and Tags will break.
   WP 2.3 totally restructured the way it deals with categories and tags. Nearly any plugin that uses categories and tags in any way will almost certainly break.

   If you absolutely one of these plugins to work, do not upgrade until after the plugin author announces that specific plugin works with WP 2.3.

2. You should create a “test blog”.
   A test blog is nothing more than a near duplicate of your regular blog. Create it at your host; its own database so you don’t “stomp” on your main blog when you test upgrading. Then install the same theme and plugins you use at your regular blog. Write a few “test” posts just to have something in the database.

   How is this used? I pre-test every plugin or widget I download on my test-blog. That way, I can identify any incompatibilities without risking taking my real blog down.

   The test-blog is especially important during major upgrades, because there is a strong possibility that a few of the plugins you use will no longer work as advertised. If you upgrade the test blog first, you maintain your old blog while testing all plugins, widgets, theme changes and pretty much everything before upgrading your public blog. This helps you identify incompatibilities, and also gives you time to identify substitute plugins for your real blog.

3. Wrap all ‘special’ ‘template tags’ calls in “if/else” blocks.
   During upgrade, you will often turn off plugins. When you do, you may see a big black mysterious error messages like this:

   Fatal error: Call to undefined function utw_showrelatedpostsforcurrentpost() in /home/…/upgradeTest/wp-content/themes/ygo-assorted/Post.php on line 38

   These blog killing errors are nearly always due to missing special purpose “template tags” a plugin developer wrote. When the plugin associated with any ‘special’ template tag is active, the special template tag calls a different block only available in only when the plugin is activated. Otherwise, you get the skanky error.

   To avoid this problem, wrap all special template tags- like ‘utw_showrelatedpostsforcurrentpost();’ in “if/else” structures similar to this:

   if(function_exists(‘utw_showrelatedpostsforcurrentpost’)){
   utw_showrelatedpostsforcurrentpost();}
   else{echo(‘activate plugin ‘); }

4. Anticipate difficulties and delays with major upgrades.
   If you use very vew plugins, your upgrade will probably be a snap. Many bloggers just click the “one click update” and they are done.

   However, if you use loads of plugins, you could have difficulties. For example, one blog visitor tells me “adSense Deluxe” doesn’t work in WP 2.3. Also, some of the various “tag” plugins with WP 2.2.X, you may need to run a script to restore functionality. So budget some time.

   Because I’m in the process of upgrading plugins, I am also aware that quite a few “hooks” available prior to WP 2.3 have simply vanished; (one of my favorites is gone!) “Hooks” are used to pull in plugin functionality at a certain point in WP; when the hook is vanishes, a plugin that uses that hook doesn’t work at all. So, in this case, you fiddling with your theme won’t help.

5. Let the plugin developer know if a plugin breaks.
   If a plugin breaks, let the developer know. If you can’t find an email address, post about the problem at your blog and leave a trackback to the blog post where you can get the plugin.

   The big advantage to informing the plugin developer is they may be able to save you time by either confirming that a) It’s not you, it’s the plugin, b) they may point you toward the fix or c) they may schedule some time to fix the issue.

   In anycase, even though the developer may be busy and unable to look or fix the issue quickly, they will want you to let them know. They are the best person to help you!

Meanwhile: Good luck with your upgrade. Mine will be slower than most because I’m updating my plugins in parallel. I think I have “HideSponsoredCategories” finished, and “KonteraControl” is next. I’m on schedule to finish my upgrade in.. how many weeks was that? Well, soon.

With luck, and effort, a new version of Kontera Control will be available next week.