WordPress 2.3 released

[SarahG]

Looks like WP 2.3 has been released

Anyone prepared to be the guinea pig and try it out? ;)

From what I've read, a few plugins are not compatible yet and those that are will probably need updating too. So that's a good hours work per site!

WordPress WordPress 2.3 (http://wordpress.org/development/2007/09/wordpress-23/)

[ses5909]

I will probably add this to my to-do list this next week.

[Jelena]

I will definitely wait a little bit before upgrading just to be sure all of the plugins I use work well.

[doorlight]

Still waiting for my plugins to be upgraded too. This makes me so stressed out. :P

[BPartch]

I upgraded last night, all went well but the tagging plug-in I had been using was not compatible, not sure if it will ever be updated so I may have to switch to the new default tagging WP offers.

[davemcnally]

I have only just got my blog online do don't think I will be trying to upgrade just yet. Unless that is, it's a simple enough process!

[SarahG]

it's usually a simple process. Depends on your plugins. For a standard install then simply delete all the files on the server besides your wp-config.php and the wp-content folder. Then upload the new files besides the wp-content folder. Check as to whether there is any change to the wp-config-sample.php file compared to your wp-config.php file. If so, alter your existing config file and upload.

Then go to yourdomain.com/wp-admin/upgrade.php and follow the steps and that's it.

Of course, you should back up your database beforehand ;)

I also tend to check if Akismet has been updated and upload that plugin file too.

[Prettyfem]

I will be waiting to make sure everything is ok (no bugs) before I upgrade.

[davemcnally]

it's usually a simple process. Depends on your plugins. For a standard install then simply delete all the files on the server besides your wp-config.php and the wp-content folder. Then upload the new files besides the wp-content folder. Check as to whether there is any change to the wp-config-sample.php file compared to your wp-config.php file. If so, alter your existing config file and upload.

Then go to yourdomain.com/wp-admin/upgrade.php and follow the steps and that's it.

Of course, you should back up your database beforehand ;)

I also tend to check if Akismet has been updated and upload that plugin file too.

I have a few plugins installed so I may leave it for now, wouldn't want to ruin something I just started and, as they say, "If it aint broke, don't fix it" right? ;)

[SarahG]

couldn't agree more. But then again if there are security fixes I usually give it a week and then upgrade. After what happened a few months back (January I think, or thereabouts) when a load of blogs got hacked over a dodgy copy or something, I prefer to wait a little while. Plus with 10+ sites to upgrade I need to build up the energy ;)

[Prettyfem]

I was browsing Digg and found this.

"Developers Admit WordPress 2.3 Spies On Users"

http://groups.google.com/group/wp-hackers/browse_thread/thread/bdced7524fa79a18/2d4e69fb46a6a947

[Prettyfem]

The “update service” sends information such as you blog URL, the version of the various plugins installed, server variables etc back to WordPress.org.


You can also read about it here.

whatithink m Not Upgrading to WordPress 2.3 (http://www.paulmc.org/whatithink/2007/09/25/why-im-not-upgrading-to-wordpress-23/)

[SarahG]

Well the blog version is always printed in your header code unless you remove it, and it's in the code to your login page too. So there's no difference in sending it back to WP either.

And from what I've heard, there is meant to be an auto check on the plugins used and to tell you if there are new versions available (or do they auto install?). perhaps sending the plugin versions back is part of this?

Personally stuff like that wouldn't bother me. With the thousands of WordPress users out there, I doubt my information is of much interest to them ;)

[kingjacob]

I upgraded from the RC2.3 to 2.3, I liked the release candidate but the actuall release is full og bugs and errors, just look what it did to digitalorder (http://digitalorder.org) all the text on my index is now bolded.

Update: I fixed it, somehow having the More tag write after bold tags was making everything else bolded.:sigh

[Prettyfem]

For those interested Matt commented on my blog about the whole spy thing.

[adalante]

I'll wait one more week before upgrading, some Plugins & Themes are not compatible yet.