hotsitez

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.

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!

JOSH –

Had 4 blogs down – Your Trick;

define(‘CONCATENATE_SCRIPTS’, false);

Fixed the issue – I can now see to edit posts, create new posts (could not write in the area) and now can again used the media button and featured item button – pops up window again!

FIXED ALL my current issues so far since upgrade THANK YOU!

And can I ask why and what this fix did? – I have 23 clients blogs to upgrade all with different plugins and custom themes, so I like to know what did I cut out or do. Thanks Again!

SoundTrip –

I believe the fix for me occurred when I manually removed the phantom active plugin from the database column for active plugins. This came in the form of a big string like ./../../../../../../../tmp. I don’t know how the string got there, perhaps an installation bug or artifact or a plugin installed left it behind. Who knows. I didn not find this string in the databases of blogs that did not exhibit this upgrade issue.

That is correct – I ran into this problem on 3 out of 11 blogs, I used phpADMIN and manually edited / removed the phantom plugin (you mentioned above) in wp_options | active_plugins – and the issues was fixed each and every time. – Thanks for the SoundTrip 2.5.1 Version error fix – lol

HotSiteZ