Tim Brownlaw

Cheers AITpro… As it turns out, this was the cause of my woes!
So a huge thanks for jumping on this and getting it sorted out!

Now I can let the hair grow back from where I was head scracthing over this ??

Thanks to everyone for adding to this…
At least it confirms… for the time being… I’m not going completely mad!

I’m just getting back into digging into this a bit deeper…
But on initial testing I get the following…

Firefox – Post WYSIWYG Dead – Widget Dragging Dead
Chrome – Post WYSIWYG Dead – Widget Dragging Dead
Konqueror – Post WYSIWYG Functions – Widget Dragging Dead
Of course this is all under Linux… Which shouldn’t be a factor!

Just to Clarify the DEAD WYSIWYG – I just get the basic text area box and the Visual and text tabs and cannot even type in it.

What is interesting that under Konqueror it works like a bought one…
That is just the editor – not the drag and drop for the widgets.
There’s a clue in there somewhere lurking!

I’ll see if I can get a working blog again for Christmas!

Cheers
Tim

Well I lept onto another site and upgraded then deactivated all plugins – running WP 3.3.2
Then upgraded it to 3.5 and that appears to be ok.

All 3 sites are completely different in their “upgraded from” version and the plugins used, so no pattern I can see from that…

@josh – I’ve tried what you suggested and still no joy on the site this first showed up on. Using Firefox at the moment!

So one site seems to be completely Javascript Challanged.. The 2nd will at least let me type in the broken WYSIWIG and the 3rd has no problem at all.

The First site – makes an attempt to read in an existing post… The Sidebar comes up and it makes an attempt to write it but then goes blank!

Seems that not ever having a problem with this in the umpteen years I’ve been using WP – it’s my turn ??

I’ll have to play with this later and get serious working out what’s going on!

Cheers

I noticed the Widgets Drag and Drop completely die so the javascript on that is clobbered in Appearance -> Widgets

Tried another site – pre upgrade – I could drag and drop to my little hearts content… Upgraded to 3.5 – BANG! Dead in the water.

I’ve disabled ALL Plugins and still no joy on both sites.

I’ve not had the time as yet to dig into this as yet but is anyone experiencing this?

@michiel – Glad you got it sorted but seems it’s not a plugin issue for myself BUT in both cases I had upgraded WP Before upgrading any plugins and then deactivated them, but I don’t see that as the issue ( he said!!! )

Just an update…

I was using KATE which chops long lines which caused the issue.

Modifying the SQL File with GEDIT – which doesn’t chop long lines – worked a treat.

FIXED and FOUND the CAUSE!

I’ve been busting my chops on this for ages…

I download and install Live WP Sites for working on client sites on my local server on different URL’s etc without issue… until now.

Everything looked just fine in the DB, config files etc… It wasn’t all the “obvious” things that can cause this…and this little script brought the Admin back to life!

So Thanks a ton xionmac! You are a champ for finding that and also thanks to Mark Jaquith for coming up with the script. It got me back to a working point.

In my case it was something in the DB as I can recreate the problem by reloading it.

In the wp_user_roles entry in the wp_options table, it turns out that there were a number of Linefeeds ( LF ) and that was upsetting the world! This must have occurred in the Export and or the Editor I was using… Making the entry a single line fixed the exported version!

I’m guessing I’ll have a few more LF friends in some other entries but at least It’s now glaringly obvious as to what was happening.

Cheers
Tim

Well after finding this out the fun ( read that as a lot of digging in the code ) way I found the same solution as mentioned here by a few others.

But the clients site had a bucket load of plugins so I had to hunt down the offending one.

So ichurakov, jeffduyndam and SocialMediaCop.com have the answer.

The Culprit is version 2.0 of the plugin.

The reason this goes BANG! is because wp_admin_css will echo the CSS link immediately and this is being done inside the constructor which is instantiated in popup-domination.php.

So I’m guessing that WP runs all the active plugins prior to doing all its other bits and pieces… basically what the guys have done is naughty!

You’ll see in the browsers source code, on the pages that show the errors, the CSS link having been sent out prior to the rest of the page being rendered and of course prior to WP doing all its other bits it needs to do. Like headers and cookies etc..

The CSS file being called doesn’t even exist in WP > 3.3.x so there is no harm in clobbering it ( whoops – commenting it out ).

So there’s a trap for plugin writers…

Cheers!