Are you sure that you have not disabled visual editor in your user profile?
Can you tell us what you have tried already? Please do try to include as much detail as possible.
Things I HAVE tried: (in no particular order)
- Disabling all plugins
- Using the default Theme
- re-installing the core WP files (not wp-content)
- Clearing my browser cache
- Different browsers/machines
- Different locations/networks
- “Use Google Libraries” plugin
- Turning on and off the visual editor from the user profile
- added
define( 'CONCATENATE_SCRIPTS', false ); to wp-config
I think that’s everything, I’ve been wrestling this issue for the better part of 2 months or more. Each of the above items has been tried several times and in various orders or implementation. So far the only thing that has definitely worked is the roll back to 3.4.1.
Thanks again for your time.
As far as detail, there is none. None of the proposed items effected the core problem. Expected changes did occur (plugins, themes) but did not effect the lack of editor. When I turned off the editor in my profile, I could then see the contents of my post as it should appear in the non-visual editor, but re-enabling the editor returned it to it’s broken state.
The only fix I have come across for this problem is to use the Google Libraries plug in.
He did try that already, mrsreeder.
Two suggestions from me.
– create a new user in the admin with the same rank as your current user, log off, re-log as the new user, and see if the problem remains. A bit more than a year ago, I had the visual editor broken with a user, while a newly created account didn’t have the problem, turned out something got messed up in the database options for the user, I ended up manually cloning, within phpmyadmin open in two tabs, the user options from one user to another. And boom, problem gone.
– some say that time is money, so if you’ve been spending hours on it already, and you’re pissed off, and ten bucks isn’t much for you, how about you try your blog on another web host, just for a couple of days ? Create yourself a godaddy hosting account – just kidding, go for hostgator or any other quality host, godaddy isn’t worth it – upload a clone of the blog to the new hosting account, change the domain nameservers in your registrar’s options, come back 24 hours later when the change is effective (or use whatsmydns.net to see if the change has propagated to you already, or update a little something in the blog’s template to see which version you’re seeing, whatever works).
And there you are, you can see, in exchange of 30 minutes and probably ten bucks, if this was related to your web host.
I think I tried the ‘user’ trick, but will do it again, because I can’t remember for sure. As far as the secondary hosting thing… I’ll have to think about it. Do you think a LAMP virtual machine with a copy of the site on my local LAN be a valid test?
While a LAMP virtual machine could run your blog, you’d have adjustements to make to have it work locally, and that doesn’t tell you it would work with another web host.
But, hey, sure, you can try it locally. I’m not familiar with the adjustments to make to have a blog configured to be online work locally, so it would take me longer than setting it up with another web host, haha ^^ If something is definitely broken inside the blog, it will also be also broken locally.
