Support » Plugins and Hacks » [Plugin: Add-to-Any] wrong save path in XML for upgrade

  • Just tried to do the latest upgrade for Add-to-any on a WP 2.7.1 install, using Firefox and the upgrade failed with the following install path showing in the result –

    …/public_html/blog/wp-content/upgrade/add-to-any/add-to-any/share_save_120_16.png

    There should only be one /add-to-any/ in the path

    Looks like a typo in the XML by the plugin author (it happens to us all) so though I’d best shout it out to give them a chance to fix it.

    Regards
    Gaz

Viewing 2 replies - 1 through 2 (of 2 total)
  • Interesting, haven’t seen any other reports of this happening. Can you offer any more details that may help? Thanks, Gaz.

    Anyone else?

    Yes – it now happens with ALL plugins on any of my non WP2.7.1 blogs

    That is – all my WP 2.6.x blogs are having this same problem with ALL plugins on ALL hosts

    Looks like something at the WP plugins directory has changed, such that 2.6.x WordPress installs are being forced to upgrade to 2.7.1 whether the site owner wants to or not – i.e. how the plugin packages are zipped appears to have changed (I could be wrong though).

    This, if true, is highly unethical as not every plugin has been, or will be, upgraded for 2.7.x and above, and some sites rely on specific plugins that will have 2.6.x as their final WP version.

    I’ve checked, and all my hosts are using PHP 5.x and MySQL 5.x so it doesn’t look like the issue that Lester Chan offered a hack-workaround for (plus the symptoms of what his hack fixed were different to this issue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: Add-to-Any] wrong save path in XML for upgrade’ is closed to new replies.