Fatal error during automatic upgrade

Has anyone experienced this error?

Thanks

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

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

and you should NOT be using a plugin to upgrade from 1.5.2

You would seriously F*ck up your db, if you even got through it.

The database changes from 1.5.2 to 2.6.3 are immense, and what you need to be doing, is incremental upgrades that are done manually.

Were this my blog, I would probably upgrade to 2.0.11

then I would upgrade that install to 2.3.3 than from there I would upgrade to 2.6.3

.. and even that might be more leaps than I would do on my own blog

There are countless posts on here where people have tried to jump from one very old version to the latest and have ran into insurmountable issues with their database that resulted in nearly complete reinstalls.

Its more work to do it the long way, but trust me, it saves tons of potential heartache in the end.

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?

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

then do all of us a favor and sh*tcan your blog.

I have been holding off because of the long-winded upgrade process.

and you have no-one to blame for that but yourself, right? You could have been keeping up with the upgrades as they came out, instead of waiting .. what three years?

I am unlikely to be able to set aside the time to do that.

Lifes a bitch, I guess.

—

Im sorry, you want sympathy from me, you wont get it. Waiting three years yo upgrade and then complaining that a plugin wont do all the work for you? (ive deleted the complete ass-whipping I want to input here)

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

Ask the plugin author.

—

Now that Ive gotten that off my chest, here’s the nice me:

Consider that in lieu of upgrading your blog is exploited. The choice is yours. Consider also, that you share a web host with countless strangers, and that all of your sites are only as secure as the least secure. At this point, thats probably yours. In other words, not only do you do a disservice to yourself by not upgrading, you do a disservice to the other people that share the server your on.

On an even grander scale, you share the WWW with a whole lot of other wordpress users. Hacked sites and hackable sites do nothing but embolden hackers to go find other sites.

Amnd honestly, its not that long winded.. I upgraded a 2.0.3 blog the other night in less than 20 minutes.

One Thing to consider when upgrading:

you do NOT need to bother uploading any of the subdirectories inside wp-includes/ .. You do need the files that are directly and immediately inside wp-includes/ but all that JS and scriptalicious crap can be left off the upload.

That one item can save tons of time.

you switch to the defualt theme.
you disable ALL your plugins.
upload just the files you need

hit upgrade.php

do it again …

its very very simple.

I do this stuff in my sleep, and if you sincerely want to get your blog upgraded, Im willing to help. I wont do it for free, but I am VERY reasonable, and I guarantee it will work when im done.

Think about it, and understand that my words up above were not personal — theyre actually intended to motivate you. Its in all of our best interest for people to upgrade.

If you like, contact me : whoo ATTTTTTT village-idiot.org and we can discuss this further.

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.

It was you that jumped down my throat for using the plugin.

I beg to differ re: that description. If I ‘jumped down your throat’ it was in the post after that where you expressed an unwillingness to go on upgrading.

but it’s easy to screw up overwriting/deleting.

No its not ?? cmon ??

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.

if by ‘wordpress’ you mean the information is available on this domain, sure. The codex is completely user-driven content. I can add to it. You can add to it. Joe the plumber can add to it.

See my point?

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

I dont know. At one point, it did. Again, user based content.

—

There were database schema changes made at certain points and that seems to be where the potholes are, along the road. There are posts, for instance, repeated posts, regarding category IDS all being set to 0 or something like that .. Thats just one I remember, because I actually helped someone out of that mess.

Now up to 2.3.3

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

no, you should be okay.

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’