Fixing Errors in WordPress 3.5

I write for several blogs seperate from mine (blog post about that coming soon), so I tend to see Wordpress updates on those blogs before I see them on mine. One of the coolest updates to WordPress 3.5 is the new Media manager for blog posts. After seeing this on one of the blogs I write on, I went to ny site and quickly made the update. You know how it always tells you to backup before you upgrade? I didn’t, and almost ran into big problems because of it. When I went to make a new post, only my text menu was available, so I couldn’t blog for several days. I thought I was going to have to go through and do a manual upgrade through FTP and multiple time consuming steps.

Before going through any steps to correct WordPress 3.5 errors, try clearing your cache. If that doesn’t fix the problem you’re having, then you have something bigger going on. There is an easy fix that I found, and it fixed my problem. The fix is to enable javascript debugging, which is disabled by default. Simply go into your ”wp-config.php” file via VTP and right before the line that says “That’s all, stop editing! Happy blogging” there should be this line of code

define('SCRIPT_DEBUG', false);

You will want to change that to

define('SCRIPT_DEBUG', true);

Be aware that this won’t fix all WordPress 3.5 errors. If it doesn’t, then you have something bigger going on. Try disabling all of your plug-ins, and if that fixes your problem then enable them one by one until you enable one and it causes the problem again, the last one you enabled is the one causing the problem.