Title: Visual Editor Not Working – Alternative Solution Last modified: August 20, 2016 --- # Visual Editor Not Working – Alternative Solution * Resolved [ronnieg](https://wordpress.org/support/users/ronnieg/) * (@ronnieg) * [13 years, 3 months ago](https://wordpress.org/support/topic/visual-editor-not-working-alternative-solution/) * Symptoms: On some WP releases, up to and including 3.5.1, the Visual editor may stop working, sometimes seemingly spontaneously, and sometimes after a WP release upgrade, server change, or even in just some browsers. In some cases, even Text/ HTML edit mode would display its content with the visibility:hidden css attribute and color=”white”, so it cannot be seen unless you select a section of it, and then only that section is visible. * Variations of this issue have been reported many times, and supposedly resolved and closed many times, at least as far as the original reporter is concerned, but never 100% for every situation. Some proposed solutions involve multiple diagnostic actions, such as: disabling all plugins then activating them one at a time, switching themes, re-installing fresh WP files, etc. If those methods work for you, and it works for all browsers, that’s great. But I tried all of those diagnostics and proposed solutions, all to no avail. What finally worked for me was a solution that included creating clones of the WP specific tinymce language file into two other locations with a file name that is not WP standard, but matched the files that failed to load according to Firefox/Firebug console debugging results. While it worked, the issue is that the next WP upgrade could and probably would wipe out the cloned files, as it does and should with any other core hack, so the problem could come back. * So my solution, based on the file cloning that finally solved the problem, was to create .htaccess rewrite rules to have tinymce load the correct file name instead of cloning the language files in a non-supported way. I simply added the following new rules to my .htaccess file: * ``` # Fix invalid language file references RewriteRule ^wp-includes/js/tinymce/langs/en.js$ wp-includes/js/tinymce/langs/wp-langs-en.js [L,R=301] RewriteRule ^wp-includes/js/tinymce/themes/advanced/langs/en.js$ wp-includes/js/tinymce/langs/wp-langs-en.js [L,R=301] ``` * Obviously, you would need to replace the language designator part of the file names to match your particular needs, if not English. * While this may still not be ideal, it could solve this issue for folks who are constrained to using a particular older theme or plugin that may not be well- behaved, according to WP Codex, or may have server configurations causing the issue and that they cannot readily access or change. Viewing 4 replies - 1 through 4 (of 4 total) * Thread Starter [ronnieg](https://wordpress.org/support/users/ronnieg/) * (@ronnieg) * [13 years, 3 months ago](https://wordpress.org/support/topic/visual-editor-not-working-alternative-solution/#post-3522844) * As I worked on this issue, I had to spend literally hours and hours searching this forum, reading each of the dozens of threads on the subject, and trying the various diagnostics and solutions people had come up with until I found something that actually worked reliably for all of my sites, not just one or two, and not just for a particular host configuration, WP version, plugin, theme or browser. Very frustrating for me, a pretty tech savvy WP user, and frustrating as well for the moderators of this forum, I’m sure. * IMO: There really needs to be a single one-post “sticky” post for this particular issue, with multiple WP developer reviewed / approved solutions, starting with the simplest: Change user settings to not disable visual editor when editing posts/pages, and progressing to the more aggressive diagnostics and fixes only if that doesn’t work, in a logical, step-by-stap process. I don’t know why or when WP changed to make that a default for all/new users, but that probably needs to be reviewed as well. * Just a suggestion. * [fluentlight](https://wordpress.org/support/users/fluentlight/) * (@fluentlight) * [13 years, 2 months ago](https://wordpress.org/support/topic/visual-editor-not-working-alternative-solution/#post-3522985) * Hi Ronnie! * Sorry if this a silly question, but can you tell me exactly which .htaccess file needs to be modified? I seem to have a few of them! Which folder is what I’m asking I guess! I would certainly love to see my visual editor working again! * Thank you, and again, sorry if it sounds like a silly question! * ~ Cliff * Thread Starter [ronnieg](https://wordpress.org/support/users/ronnieg/) * (@ronnieg) * [13 years, 2 months ago](https://wordpress.org/support/topic/visual-editor-not-working-alternative-solution/#post-3522986) * Whichever is in your root folder where your WP index.php resides. * [fluentlight](https://wordpress.org/support/users/fluentlight/) * (@fluentlight) * [13 years, 2 months ago](https://wordpress.org/support/topic/visual-editor-not-working-alternative-solution/#post-3522990) * Thanks much, man! Unfortunately no dice though – still no luck with getting the visual editor to show! If I find any other solution, I’ll be sure to update this comment. Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘Visual Editor Not Working – Alternative Solution’ is closed to new replies. ## Tags * [visual editor not working](https://wordpress.org/support/topic-tag/visual-editor-not-working/) * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 4 replies * 2 participants * Last reply from: [fluentlight](https://wordpress.org/support/users/fluentlight/) * Last activity: [13 years, 2 months ago](https://wordpress.org/support/topic/visual-editor-not-working-alternative-solution/#post-3522990) * Status: resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics