Visual Editor missing and broken in 3.1

Hi Werendle, thanks for the suggestion. I’m glad you got your problem sorted. However this doesn’t sort this problem as there is NO visual editor at all (see image link on flickr) so no show/hide kitchen sink button to click.
https://www.flickr.com/photos/60163908@N04/5515622066/

Thanks for the support though, I appreciate it.

And now for bizarre news…

We took a break for the problem for a while. Today, my husband decided to post a movie review, since HTML works fine. Everything was back to normal. NORMAL??? We made no changes. We did not add or delete anything. The visual editor is working normally now. This is beyond strange.

Yes, we did reboot the computer. We did that several times during the visual editor problem and it didn’t make a difference then. Otherwise, I’m without a clue. I realize that this doesn’t help, but I figured the update could be useful to someone.

Just installed 3.1 yesterday and have the same problem in visual edit (no toolbar). I am not a web developer and do not understand any of the suggestions above.

I’ve always updated via ‘automatic’ without problem and this is very upsetting.

If there is no fix, how can I return to older version?

Have you tried:

– checking through Troubleshooting WordPress 3.1 – Master List

– 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 Ten 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 the wp-admin and wp-includes folders from a fresh download of WordPress.

to fix it just adding define(‘CONCATENATE_SCRIPTS’, false );to wp-config.php and you get working visual editor… good luck

Thanks, I was able to get it back by deactivating plug-ins and then re-activating.

Glad to know you got it back. ??

Please mark thread as “resolved” using the dropdown in the right panel so that:
– others with similar problem can see it as “resolved” and will read this thread for help if they have similar problem.
-volunteers providing help see it as “resolved” and will not waste time reading it.

Would be happy to mark as ‘resolved’, but there is no option for it on this page. Sorry.

Hi t-p this is not his thread, so he can’t mark it ‘resolved’ it is now midnight in the UK, I will try the most recent fix in the morning, fingers crossed it will work, I have tried every other suggested solution to no avail.
Many thanks
theMightyAnt

I don’t see how hitting “resolved” when other users on this thread are NOT AT ALL resolved is even ethical. “themightyant”: thank you for laying out the case clearly. Amen to everything you said. My problem was across FF, Chrome, Safari, IE. I will be interested in seeing what happens when my host, Netfirms, which has just been purchased, finishes migrating. Over the period of my initial posting, I was finally getting emotional in my writing, and was reprimanded for posting on several like threads. But how are you supposed to learn anything if you don’t read all the threads and try all the suggestions? And then to post the results so others don’t feel alone.

Your patience here has been monumental. But in the end, all you will get is silence. Existential statement, I know. But I am smarting from this experience.

my “fix” has been to go back to 3.0. Some fix.

themightant.
Have you resolved your issue? Because I’m having the same problem with one of mine.

I have 2 wp sites on the one hosting account. Use FF. Only 1 site is having this issue.

Have also done all the above suggestions with no success.

Don’t want to hear from anyone that its a hosting server issue because its not. Have 3 other clients using the same hosting & no problems with their wp sites.

I am very disappointed that you’ve knocked out the server possibility. All my hopes were pinned on the otherwise disturbing sale of my host to some unnamed and probably more expensive company (a la Mozy). I’m still running 3.0 as my fix, which means that I’ve tried everything to no avail. It’s so odd – every suggestion made has worked for some but done nothing for others. I wonder what tiny line of code in the new version could be so widely applied.

As I understand it, the menu bar and other items in the editor are javascript driven. For several having a problem, deleting the wp-includes and wp-admin folders and reinstalling new wp files has helped. In a previous version, some time ago, one person did this three times before having any success.

You can check your java here, https://java.com/en/download/installed.jsp?detect=jre&try=1

WP 3.1 has been installed successfully on thousands of computers so the question is what do you, kbarncat, Expressions and themightyant, have in common on your setup other than just wp 3.1?

.htaccess files? And

Don’t want to hear from anyone that its a hosting server issue because its not. Have 3 other clients using the same hosting & no problems with their wp sites.

does not rule out the server issue unless all three are on the same server.
Do your hosts have something in common? Windows or Linux servers. Error logs on the server?

This is an excellent answer. I will check the Java. But isn’t the Java an individual computer factor? I work in two stations, one a lap top, the other a desk top. They run different versions of SnowLeopard (for various reasons), and I imagine, then, that their Java is also different. The desk top is regularly updated. The lap top is not. So it’s not a problem with display on individual computers.

Okay – as to set up, Mac in various configs. Netfirms uses Linux servers. Not Windows servers. I am using a variation of 20-10, but 20-10 does the same thing when I switch to it. When I have the courage to re-install, I’ll do it manually, and I’ll try the includes and admin folder replacement – though that seems very mysterious to me – especially the three time replacement. (Logic? Is this an argument for A/I?)

I run only Askemet and comment subscription. Mine is a very simple setup. I have about four blogs, all on the same server – some of them have not been updated, some have. The ones I took to 3.1 – all different themes and plug-in set ups – all had this problem. So it really does feel like a server thing.

I’ll have to google .htaccess files.

Thank you for this measured, logical and informative response.

I meant, I’ll try it manually again – but from the get-go.