I wrote this same blog post on my company site “lite-code” earlier today because I was having a issue with the Wordpress Visual Editor, it wasn’t working, at all. I couldn’t even use the HTML Tab to work that way just to make a correction to some page content I mistakenly uploaded. To get around this temporarily I went to “Users” and then the Admin of course. And once you are in there you will see a check box that says “Disable the visual editor when writing”, click that and save changes. Now you can at least view your post or page content and use raw HTML or plain text. Read below to solve the TinyMCE issue I was having. Hopefully this will help someone out there.

Source: The vanishing “Visual Editor”

I use Wordpress at least 20 times a day (if not more) for random tasks, posts or reading other blogs to troubleshoot or diagnose issues. The other day on a blog I have been working on for a client for almost a month now, the Visual Editor within Wordpress disappeared for no reason. I didn’t run any updates or install any new plug-ins.

So what I did was located the TinyMCE.php file through my FTP client (FileZilla), then attempted to run the PHP file through my Mozilla browser. I kept getting Server 500 errors everytime. I tried this with another blog, and voila the PHP script ran properly with no errors. So I then back tracked it to see if there was any difference in the files within the folders and noticed right away in the wp-includes folder there was a .htaccess file that none of my other blogs had. I simply deleted the file and what do you know….? The Visual Editor showed up once again and has worked flawlessly.

Now, I have no clue as to how the .htaccess file was created and put there, but for some strange reason it was. I had a hard time finding any answers to this question on the Wordpress Support Forums, but I did find one post that was regarding the issue, but no one there seemed to have a solid solution to resolve the issue. There was the typical “Restore a backup” (Which I did numerous time, with no avail), and of course “Run the 2.9.1 update” (Which also did nothing for me).

This is not guaranteed to fix your issue, but who knows, it might. I posted this to help anyone else who has this issue as it seems like lots of people do. Feel free to contact us if you can’t resolve the issue yourself.