Fixing the “visual editor not working” in wordpress.

My visual editor has not worked for sometime. Don’t exactly know from which update. It at least did not work in 3.5.1 and 3.5.2.

Did some googleing and found several posts with many solution, but none of them worked for me.

Tried adding the line to wp-config.php:
define( ‘CONCATENATE_SCRIPTS’, false );

Cleared browser cache and logged in again. Didn’t work.

Next I tried was to delete my wp-includes folder and then copying it back from the tar.gz installation file. Edited a post and did a page refresh. Then the editor worked again.

Not sure excatly what was wrong, but at least now it’s working again and I didn’t have to do a full reinstall of WP.

This entry was posted in Technical. Bookmark the permalink.

10 Responses to Fixing the “visual editor not working” in wordpress.

  1. fulgerica says:


    I had the same problem today , after upgrading to wordpress 3.5.2, the Visual edit dissapeared. I tries – just like you – all sollution found on web. Thanks to your method now I had fixed. So, it works deleting the wp-include and re-copy it from the tar.gz archive.



  2. lars says:

    Happy to hear it worked for you too. 🙂

  3. NDLee says:

    Interesting. I got the same problem and i’ll try it asap.

    Thank you!

  4. Elena says:

    Worked for me as well. Thanks a lot.
    (this message is just to give my thanks and reinforce the method)

  5. Have the same problem too after upgrade to 3.2.5. Visual editor, postbox container, and the whole interface in admin post-edit not working. So, i look on the jetpack plugin. After i deact and reactivate it, the editor back to normal. I feel lucky ! 😀

  6. Darko says:

    You are the master man! You save my live! Thank you!

  7. piqueturns says:

    This may sound stupid but how/where do I access the tar.gz archive file to recopy the wp-includes folder?

    • lars says:

      Just download it from You can also download the ZIP file. Remember to back up beofre launching. Download the version corresponding to whatever version you are running. I just renamed and uploaded the folder. Then I switched names an checked that everything worked. Easy and fast to revert if something goes wrong.

  8. Martin says:

    Your fix actually caused my clients site to stop working, internal 500 error, reverting back to previous wp-includes folder did not help…its totally screwed now.

    • lars says:

      The wp-includes folder is as far as I know just static php and js files. If reverting back the original wp-includes folder don’t work then something strange must have happened.
      I think php is case sensitive. May it simply be as simple as a capital letter in the wp-includes name? Is the WordPress installation heavily modified?

Comments are closed.