WordPress Automatic Upgrade Plugin: Update

Here’s a quick update on the WordPress Automatic Upgrade by Keith Dsouza and the problem with the DoFollow plugin by Kimmo Suominen (see previous post). Currently, for those of you using the DoFollow plugin and wish to use Keith’s automatic upgrade plugin, you must deactivate the DoFollow plugin before running an automatic upgrade then reactivate DoFollow plugin after the upgrade is finished.

Keith’s working on a fix for the problem. Here’s an excerpt from his comment about the matter:

Found the bug, it’s apparently no one’s fault but there is some code in the DoFollow plugin that breaks the entire operation.

In there on line 44

if (is_plugin_page()):
$wppDoFollow->options_page();

is causing the problem since the plugin was not activated already the method throws a fatal error and the plugin fails, the reason you may have seen a blank page is because your server settings are not set to show you errors or something. But I am fixing the errors right away and will release patched version which will continue without activating the plugin and show the user a message about it.

His patched version should be out soon but as long as DoFollow is deactivated beforehand and reactivated after then there’s no reason not to start using the plugin right off.

Upgrading your WordPress install just got a whole lot easier!

Update 08-08-07: Keith has just released a new version (0.5) which fixes the bug where the DoFollow plugin and certain other plugins cause WordPress Automatic Upgrade to hang when attempting to reactivate your plugins after the upgrade. It checks every plugin before attempting to reactivate just to see if it might throw an error in the reactivation process and if it finds a particular argumentative plugin (like DoFollow) it leaves it alone and reminds you to reactivate the plugin(s) manually at the end of the upgrade process. You can find a better explanation and the download for the new version here.

I tested it myself and it works just as Keith says it will. Good job Keith!

Technorati Tags: , , , ,

Comments

WordPress Automatic Upgrade Plugin: Update — 7 Comments

  1. Pingback: WPAU Bugfixes and Updates « Techie Buzz

  2. I enjoy both the automatic upgrade, and the do-follow plugin. However, I did not realize they didn’t work togehter. I guess I have to check up on this then, and get the new version. Thanks :)

  3. Hi Jakob,

    The new version does just what it’s supposed to do and I actually prefer it this way rather than have the attempt to make the plugin absolutely compatible with every other plugin out there (how many are there?). That would be an impossible task now wouldn’t it? :)

  4. Hi Luca,

    I just checked Quadreria and it appears to be working okay so perhaps you solved your problem already? If you’re still having some problems, follow the link in the beginning of the above post and let Keith know what they are. He’ll be better able to find solutions for you since he;s the plugin author. I just gave him enough information so he was able to fix a couple of bugs.

    I like your sites! Too bad I can’t read Italian though. Using “Babel Fish” only works to a point.

  5. Hello,
    just using the WPAU and at the end of the upgrade process, the site shows only white page and always redirect to /wp-admin/install.php.
    Any idea is welcome,
    Thanks for reading.
    Albert

    • Albert – I need a bit more information in order to find out what went wrong.

      What version of WordPress did you upgrade from? I’m assuming that you upgraded to the latest version of WordPress (2.8.5)

      Did you upgrade manually or via the built in auto-upgrade feature?

      Did you disable all your plugins before upgrading (if you upgraded manually)?

      Initially, if you’re being redirected to “install.php” that either means that you need to clear out your browser’s cache and reload the page (the “lucky” way) or that your WP install is not seeing your blog’s original database and is creating a new one as if this was a new install (the “not-so-lucky” way). This can mean there’s a problem with your “wp-config.php” file as this is the file that points your install to the correct database and has the DB username and password. If you upgraded from a very old version of WordPress to the latest then there’s the chance that the old “wp-config” file will no longer work and the settings have to be transferred over to the latest version of the file (included in the download of the latest version of WP–file called “wp-config-sample.php”).

      Either way, I need that information and then we can go from there.