Upgrade

So, don’t upgrade. The 2.0 series is not broken. There’s no real reason to go to 2.1 if you don’t want to deal with the hassle at this point in time.

2.0.x will be maintained for some time to come. They released a 2.0.8 upgrade for a security issue after 2.1 came out, after all.

And if you don’t want to use WordPress, don’t use it. You’ll get no argument here. It’s free to use and just as free not to use.

I thought 2.1 was a major security release and so a must upgrade?

Just explain this to me – if my site is hosted on a ccgi server and called https://[email protected]

Exactly what am I supposed to type in to the browser in order to see and run the upgrade script?

All I get now is an error:

Script is not executable. Issue ‘chmod 755 filename’

I would like to be able to get this to work but it’s just too complicated. I got 1.5 to upgrade to 2.01 so why is it failing now?

I just do not get it

I thought 2.1 was a major security release and so a must upgrade?

Nope.

Just explain this to me – if my site is hosted on a ccgi server and called https://[email protected]

Exactly what am I supposed to type in to the browser in order to see and run the upgrade script?

I don’t understand how you can have an @ sign in the url like that. What’s your blog address?

If it’s https://example.com, then you’d go to https://example.com/wp-admin, just like you usually do for logging in as the admin. It will detect that you need to upgrade and give you a link to click to do so.

All I get now is an error:
Script is not executable. Issue ‘chmod 755 filename’

See, this suggests that you broke something unrelated to WordPress.

I would like to be able to get this to work but it’s just too complicated.

It’s really not complicated. As with most things, people make things more difficult than they actually are. All you really have to do is upload the new files. But we cannot tell you how to do that. We don’t run your server. We don’t know your system. The code is generic, individual hosting plans are not (though they are similar).

It’s not an @ it’s a . (my error). I unzipped the upgrade and then uploaded the files using CuteFTP after first deleting all the old ones from the server(apart from those the instructions tell you not to).

Then I access my normal site and get the chmod error!

It should be:

https://ccgi.btbonline.plus.com/wp-admin/upgrade.php

Update

OK this is a ccgi server permissions issue for scripts that I had forgotten about since my last install. Why on earth the install/upgrade instructions can’t mention that you need to reset poermissions on your scripts before upgrading as a reminder I don’t know – it;s not like I install WP every week.

Now set and upgrade shows and executed.

Done (at last)

Please don’t plan on issuing any new versions!!!

Most servers don’t require to have permissions set to execute PHP code like that. Guess yours is weird. ??

Otto42 – are there any instructions for upgrading to 2.0.8?

textcentric: The upgrade from 2.0.7 to 2.0.8 should be dead simple, as it doesn’t require a database change (I think). Just replace the files and go.

Thanks Otto42.

I’m upgrading from 2.0.3 to 2.0.8. Is it the same routine i.e. just change replace the files?

Also, do I have to replace the plugins folder?

The upgrade is basically the same for all versions.
1. Deactivate all plugins.
2. Backup everything. Database and files.
3. Upload the new files, replacing old ones. If you’re confident in your FTP’s ability to overwrite files, use that. If not, delete the old files first.
4. Load the normal wp-admin page up in a browser. If you need to upgrade the database, the admin page will tell you to do so. If not, then it won’t.
5. Reactivate your plugins, one by one, and look for any updates for them in the process, in case they need to be updated. Never hurts to keep them up to date anyway.
6. Major updates (like from 2.0.x to 2.1.x) may require changes to your theme. Find a new version of the theme or make the necessary changes yourself.

That’s pretty much it. All the rest is detail.

Oh, and 2.0.9 is out now, along with 2.1.1. Might want to get one of those instead of 2.0.8.

Thanks Otto42 – I really appreciate that