WordPress 3.3 back to wordpress 3.2 after update

Well WordPress 3.3 is out and it has some changes to it. The most obvious one for WordPress site users is the drag and drop interface for media uploads in WordPress 3.3 which replaces the browse and upload in WP3.2.

Whoops was WordPress 3.3 released too early?

However that update to WordPress 3.3 has not gone without problems. Behind the scenes the WP team have also changed the way that the tinymce (WYSIWYG) editor is called. And this is where most of the problems is occurring on updating to WordPress 3.3.

WordPress 3.3 problems with tinymce editors and javascript conflicts.

The editors are disappearing – especially in WordPress themes and plugins that do not use standard tinymce calls. Sometimes when they do appear they do not work correctly.

Even using the new editor api call can lead to problems as there seems to be a lot of javascropt and in particular Json clashes. I expect a emergency WordPress update patch to be issued soon. There’s just too many problems with the conflicts for it not to be associated with a core issue.

I tried to add a tinymce editor to a basic WordPress textbox and while the editor appeared without a problem using the editor api call it did act very strangely.

How to change WordPress site back to WP 3.2.

So if you’ve updated your WordPress site to WordPress 3.3 and need to urgently go back to WordPress 3.2 because your web site functionality has been broken then don’t worry because reverting back to your old copy of WP is very simple to do.

The first thing you need to do is download the previous version of WordPress from the official wp legacy site.

Then unzip the file onto your desktop. Fire up your ftp programme for your web site and delete the following folders on your server. wp-admin and wp-includes.

Replace those folders with the ones on your desktop version of wordpress. Visit your site homepage and you may be asked to update the database. Click update.

Then this is very important go to the root of your ftp site and make a copy of the wp-config.php.

Do not read any further than this until you have back up a dopy of this file on your computer.

This WordPress file contains your database authorisation, if you overwrite this file your WordPress site will not be able to connect up to your database.

Have you made a copy of wp-config.php?

Are you sure you have made a back up of wp-config.php? Good we’ll now move on to the next stage of reverting back to WordPress 3.2 from WordPress 3.3.

You now need to ftp across all the root files from the copy of WordPress on your desk top to the root of your WordPress installation. These are the files like wp-atom.pnp and wp-blog-header.php.

Once you’ve done that you need to reload that backed up copy of wp-config.php back onto your server, replacing the one that’s there. This will ensure that you have not over-written all your database details.

WordPress site back to its old ways.

You should now be back up and running the old version of WordPress 3.2 and everything should be back to it’s old glorious self.

Keep you eyes open for the almost certain WordPress 3.3.1 update coming out soon.