Visual Editor Not Working

The Solution – Upgrade to WP 3.2.1

When I upgraded to WordPress 3.2, the Visual Editor for Posts and Pages stopped working. (Read below for a more detailed description and discussion).

The solution is to upgrade to WordPress 3.2.1 (Thank you WordPress Devs!)

Don’t forget to empty your cache before you check to see if this upgrade solves the problem.

Don’t Hack the Core to Solve This Problem

Sara Anderson suggested a solution to this problem (read about the problem below) on the WordPress Support Forum. She wrote:

Anyway, for us, our fix was to open up wp-admin/admin-footer.php and comment out line 36

do_action('admin_footer', '');

This worked for me. Thankfully. I think it may be a bug so if anyone knows how to report it to the WordPress Devs, please write me. And many thanks to Sara.

The Problem – Visual Editor is not Working since Upgrading to WordPress 3.2

Ever since upgrading to WordPress 3.2, the Visual Editor does not work for Pages and Posts on one of my sites. Also the Admin Bar does not appear on these Admin pages. To try to fix the problem I have done everything mentioned on this thread:

The site with the trouble is using mySql 5.0.90 and PHP Version 5.2.12. However everything works fine on my local dev site with exactly the same plugins and theme where I am using MySql 5.5.11 and PHP Version 5.2.9

I have deactivated all plugins.

I have un-installed some mu-plugins.

I have reinstalled 3.2 automatically and manually.

I have checked all permissions for files in the root folder, wp-admin and wp-include folders and they are all correct.

I have changed the theme to TwentyTen and TwentyEleven.

I have emptied my cache each time after making a modification.

And I have tried numerous other solutions suggested.

The problem persists. Here is a screenshot of the Edit screen without the Visual Editor.

No Admin Bar Images


22 thoughts on “Visual Editor Not Working

  1. I have the same problem. You described it very well. This seems like a big problem with WordPress 3.2. I hope your post will help get it fixed quicker.

  2. Can you view your admin page source code and see if it’s completing properly? If not then I’ve posted up a fix on the thread you link to. Would be interesting to know if it’s the same issue that we found.

    • I’m having the same issue and with the same screens as was taken here. I thought I’d try your suggestion… but I’m a bit puzzled.. as I don’t seem to have the “exact” line you’re listing.

      This is what I can find:

      <?phpdo_action('admin_footer', '');
      do_action("admin_footer-" .

      All are close to the line you suggested commenting out.. but not quite the same.. which one of those do I comment out?

  3. Please put that line back! Removing it will cause all sorts of problems. 🙂

    The issue is you have a plugin that is causing a JavaScript error somewhere in the admin. This breaks JS behaviors. Check Firebug or the webkit console, just update all of your plugins (and if necessary, deactivate them until you find the culprit), etc., and you should work it out.

    The error wasn’t actually caused by WordPress 3.2, but by an updated jQuery library.

    • Thanks Andrew for contacting me. I have updated to 3.2.1 and put the do_action('admin_footer', ''); back in wp-admin/admin-footer.php and the Visual Editor now works. I really appreciate your concern about this issue. And I am sure you are right but I spent alot of time trying to figure this out and searching for answers and if you read what I have written above I had deactivated all my plugins and changed to the default theme and the problem persisted. Thankfully 3.2.1 solved the problem. Thank you for your hard work.

      And I have edited my entry above so visitors won’t be tempted to hack the core.

    • HI Andrew:

      With respect,I don’t think plugins is the issue at all – at least for me. I’ve disabled all plugins as well – as Sarah below me has mentioned doing below – and done an upgrade to 3.2.1,.. tried clearing the browser cache. and that has not addressed the issue. – for me at least.

  4. @ Andrew – on the site that this was tested on, all plugins were disabled and it didn’t fix it. All files were manually reuploaded, and it didn’t fix it. This was being tested on several computers, and all had the same issues (and all caches were cleared).

    The suggestion was a temporary one as I would completely agree at hacking the core is never a good thing, however as the script was failing from that point on, then commenting out the do_action line would make no real difference to the current state of the admin anyway as that, plus all subsequent action hooks were not loading. So by not commenting it out, and not finding any other solution e.g. plugin, corrupt files etc. meant that everything from that point on wasn’t loading, or by commenting it out then it meant that at least most would load. True, it wasn’t/isn’t the best solution but at the time it was the only one that could be found and was simply offered as something to try and perhaps a starting point to find the real culprit (which obviously has been found now anyway).

    Now an update is out it’s all irrelevant anyway if it’s fixed it. Personally didn’t suffer this on 40+ sites so it’s hard to look into the source of the issue especially when the one site it was on had no error logging available.

    • @SarahA I appreciated your solution, since it fixed the problem for me and I knew it would be temporary. I just wanted to warn less careful and knowledgeable users that the upgrade solved the problem. Thanks for your help.

  5. My issue came with the jQuery upgrade that WordPress 3.2 introduced. I use jQuery on the site outside of WordPress so have disabled the built-in version so I don’t get 2 script tags that include jQuery.

    This fix may not be typical, but it could be a place to start looking if you are still having issues.

    I use the following code in my functions.php file of my theme. It didn’t have the is_admin() conditional before.

    if (!is_admin()) {
    add_action( ‘init’, ‘my_deregister_stuff’, 100 );

    function my_deregister_stuff() {

  6. I updated a blog to WP 3.3. Now I’m having the same problem as everyone else. I haven’t updated or added any new plugins. That leads me to believe that it’s a 3.3 change that’s driving this issue.

  7. Daniel,

    Thanks man. Adding the Hotfix plugin did the trick. I’m actually hosted at Joyent too, so I am familiar with php.ini file. Made the changes and I’m back to posting again.



  8. Solution :
    Step 1 : Change the theme
    Step 2 : Clear the cache
    Step 3 : Go to your editor
    Step 4 : Change to ‘HTML’
    Step 5 : Change to ” Visual Editor’
    Step 6 : Now you can find the Visual Editor Options
    Step 7 : Change to your original theme

    If Problem Persists, Add ‘ WP-Super Edit / Use Google Library ‘ Plugins, then check it. 🙂

  9. I also had a similar problem. I noticed that it was a conflict between two plugins: Ultimate tinyMCE and WordPress Visual buttons editor. I deactivated one of them and everything was back to normal.

  10. Just to add a litle spice on this conversation. I’ve installed WorPress 3.3.1. Everything worked just fine in localhost, but problem occurred after uploading on public server. First I’ve checked installed plug-ins and found All In One SEO Pack causing the problem

  11. I accidentaly forgotten to deactivate Contact Form 7 plug-in. When both of Contact Form 7 and All In One SEO Pack are active, problem persists. If I activate each of them separately problem disappear. I hope this solution can help someone else too.

  12. Visual editor used not to work for our site. We tried some of the tricks provided on various sites. First, it become good after disabling and enabling all plugins but its a troublesome task. So, I added this line define(‘CONCATENATE_SCRIPTS’, false); to wp-config.php (checkout how to do this at and it worked.

    We think javascript concatenation make problems as all javascript is concatenated for all plugins. So, adding this line to wp-config.php removes javascript concatenation and site works well. Of course, admin loads little slow but at last, it works! 🙂

Leave a Reply