Many thanks

——————————————————————————–
Dan owner of the future gadgets blog future gadgets and inventions

Thanks,
Jim Mirkalami

PS: I am a single dad. ;)

Regards,
Jim Mirkalami

Yeah, exactly. I understand why they had to act quickly to close open security holes, but yeah, hope they do a propper solution for a next update.

”
Do you know if they’re planning on implementing a better solution in a future update? Have you taken this up with them?”

I don´t know if they´re working on a better implementation. When first noticing what´s up with 2.3.2 i searched on wordpress.org and found this topic there:
http://wordpress.org/support/topic/149522?replies=4
and wrote a reply, well, let´s see.

@Hendrik: Nice one. Updating from SVN tags definitely sounds easy but how do you handle your customized wp-content folder? Do you have a symbolic link to a separate folder or something?

If you make changes to files controlled through SVN, it will try to merge them with the upstream changes when you do an svn update or svn switch. New files are simply ignored by SVN (it doesn’t touch them).

The very worst thing that can happen is that there is a merge conflict that needs to be resolved manually, but the chances for that are slim as long as you haven’t been messing with the WP core code (or something like the bundled Akismet plugin) too much. ;-)

@Folkert: Glad to hear yours did :)

@Ryan: It definitely is more of a hassle to write a plugin but well worth it. I found the hardest part to be finding information about writing plugins. There’s great information out there, it’s just not all in one place.

@Adrian: Thanks for the link. Reminds me that I need to re-enable Google Analytics. I’ll probably use it :)

@J.F.H: Cool, thanks for the sharing the links. I’ll check them out. (Have I become a plugin junkie too?)

@Hendrik: Nice one. Updating from SVN tags definitely sounds easy but how do you handle your customized wp-content folder? Do you have a symbolic link to a separate folder or something?

@tomsamson: Sounds like they did a quick and dirty patch. Do you know if they’re planning on implementing a better solution in a future update? Have you taken this up with them?

@sascha/hdrs: I’m assuming that you were upgrading from a slightly older version of WordPress? I had this happen when upgrading from 2.0.x to 2.3.1. It initially broke the version of K2 I was using. However, the latest version of K2 works well. I also haven’t had any issues with any of my plugins. Have you had a chance to see if the plugins you’re using have been updated for 2.3.x?

“This is sadly just partially true.”

Seconded!

Somehow the v2.3.2 upgrade decides to delete the wp_post2cat table from the database which is used by some plugins! Glad I did a db backup!

This is sadly just partially true. True in so far that nothing should break on your end due to changes you made. Updates can of course still break many things if the side releasing the update (wordpress) has changed things in unexpected manner.
In case of wordpress 2.3.2 they did some security fixes. Good by itself, but the way they did it is partially strange.
For example before there was the issue that one could abuse xmlrpc to see private posts and drafts when logged in in subscriber role (so a security issue). Now instead of fixing that issue in a way that when using getRecentPosts method and only beeing logged in as subscriber it only returns public online posts, they changed it so that when one isn´t logged in in admin role getRecentPosts doesn´t work at all anymore, so one can´t see public online posts anymore either.
This is quite a bummer for people who use xmlrpc in some custom blogging software (XMLRPC is meant to be a public api for use in such systems).
So yeah, regarding that its not all shiny with the new update.