idf

Now at 2.6.3

No problems along the way.

I have kept my old modified default theme for the time being and will need to copy over my mods to the ‘new default’

Now up to 2.3.3

Would you recommend another intermediate step between here and the latest release?

I would have upgraded 3 years ago to v2 but when I initially read the instructions it seemed extremely long winded, especially when it started going on about being careful which files not to delete etc.

The first 3 steps (backups, default theme, disable plugins) are simple, but it’s easy to screw up overwriting/deleting.

I also held off initially because v1.5.2 was mature and still supported, while v2 went through several bug/security fixes in its early stages.

All the posts about it going wrong meant I didn’t want to try it unless I could devote a whole day to retrieve the backup. That’s why the plugin looked useful. It is after all recommended by WordPress at the top of the upgrade instructions and it is wordpress who state that it is 1.5.2 compatible.

I’m not after sympathy – I wasted a couple of hours trying to find why it didn’t work, so I posted the reason for the benefit of other wordpress users who may be getting the same. It was you that jumped down my throat for using the plugin.

Also, why don’t wordpress suggest the 2.0.11 – 2.3.3 – latest route?

Prior to this post, I have in fact moved to 2.0.11 as you suggested (after finding the archives) and I will be moving to 2.3.3 shortly.

Rather than trying to do everything over ftp, I modified a backup of my site offline and uploaded the lot together and the upgrade worked fine.

Well that’s all the more reason not to bother at all then.

I have been holding off because of the long-winded upgrade process. Having to repeat it several times means I am unlikely to be able to set aside the time to do that.

Why is the plug in shown as being 1.5.2 compatible then?

Not a solution but a clue. Apparently the function current_user_can() was only introduced in WP v2, so WPAU will never work with v1.5.2

Yes, I have, just now – not having much luck finding a solution

I get exactly the same error as howbowers (also on v1.5.2)

“Fatal error: Call to undefined function: wp_get_current_commenter() in /…/wp-content/plugins/share-this/share-this.php on line 636”

I note that Alex’s reply is that it probably doesn’t work in 1.5.x. A shame since the compatibilty page does say that minimum version required is 1.5.