Big problems in 3.5 need more specific instructions

Have you tried:

– deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

– switching to the Twenty Twelve theme to rule out any theme-specific problems.

– resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

– re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.

I cant find where to write this????

If you mean this literally, you should open up wp-config.php and add those forementioned lines. That should do the trick!

ESMI – your step is correct to try, and I would attempt first also, but this is a Common Error arising in this WordPress upgrade to 3.5 – the ability to not be able to edit posts, create new posts, use the media or featured item tabs, etc. is not caused by plugins or theme issues. It is a bug in 3.5 and by Adding:

define(‘CONCATENATE_SCRIPTS’, false);

to the wp-config.php file will correct, you dont need to set debug to true (unless you want to).

as henrikj mentioned will fix the majority of issues people are having.

Cheers!

the ability to not be able to edit posts, create new posts, use the media or featured item tabs, etc. is not caused by plugins or theme issues

I’m sorry, hotsitez, but you are mistaken. The types of errors you are describing are not caused by a bug in WordPress, but by anything that interferes with Javascript loading. This can be out-of-date plugins, incorrectly written themes, or bad server configuration issues.

The workaround you describe is a work-around, not a fix. Turning off script concatenation may cause your site to slow down from all the script loading, due to the larger number of javascript related HTTP requests that must be made.

In other words, while that will work to get your site working for now, it is not a solution.

Also, please stop posting the same thing over and over into other people’s threads. If you have a problem, post your own thread instead. We are focused on finding real fixes here, and determining the root cause of problems. Telling people methods to work-around the issue does not help us or them.

Samuel Wood (Otto) –
We will Agree to disagree on this case (on many instances I agree) but I had even a new install with NO plugins having similar issues – and that fix corrected the problem as well as now correcting issues on 8 clients websites having aforementioned issues. So while going thru the basic steps is important that fix seems to be a big temporary solution – while not a fix, many need a temp solution while a fix is in the works. I have stopped having clients upgrade to 3.5 until I find a fix.

Sorry I was trying to comment on what was working an helping others it what I tend to do, and I have only helped and commented about this in two threads, no need to be rude when other people try to help others.

that fix seems to be a big temporary solution

It’s a server-specific solution. It simply means that your server(s) cannot handle concatenated javascripts. But, in terms of the overall issues experienced by people upgrading to a new version of WordPress, it’s very low down the lost of possible solutions. The biggest culprits are almost invariably incompatible plugins followed by incompatible thmes.

Off the top of my head, I’d say it helps in about 1 in 50 or more cases.