TinyMCE Visual Editor not Working After Upgrading WordPress? READ THIS!!

  • j893

    (@j893)


    11 years, 5 months ago

    I believe I have found a DEFINITIVE solution to this bug that has plagued WordPress users for YEARS. For those who mysteriously find their editor (and sometimes other scripts) not working after an upgrade to the latest WordPress version (and who are not helped by changing their theme etc.), here is what is likely happening, and what you need to do:

    Use PHPMyAdmin (or another database editor) to search inside your WordPress database in your “ngto_options” table for the record called “can_compress_scripts“. and if it has a value of “1” for the “option_value“, change this to “0” and save the change. You will find your editor working again! (Note: Sometimes this record won’t even exist, so in that case you need to add it. Look for a WordPress database that does have it in order to see what you need to add.)

    “Wait! Why did this happen in the first place??” you ask? Explanation:

    When you update your WordPress version, it does a ONE-TIME-ONLY test of your server environment to see if it supports compressing using the “deflate” method, if it thinks it detects that your server supports this, then it will set “can_compress_scripts” “option_value” to have a value of “1”. But it OFTEN gets this wrong! (or it just doesn’t do “deflate” correctly etc.)

    Then because that test doesn’t run again, you are stuck with an auto-screwed-up WordPress install that won’t work unless you know the above secret, or unless you use the “define('CONCATENATE_SCRIPTS', true);” directive in your “wp-config.php” file (but using that directive disables BOTH concatenating and compressing of all scripts, which makes your site SLOW!!).

    I did a painstaking MANUAL EYEBALL database compare (of a database backup I luckily made just before the WordPress upgrade) and spent HOURS tracking this down because I wasn’t satisfied with downgrading, restoring to a backup, or disabling script concatenation. So I hope it helps you all.

    To understand more about this, look here:

    Script loader updates

Viewing 2 replies - 1 through 2 (of 2 total)
  • Lucas Karpiuk

    (@karpstrucking)

    11 years, 5 months ago

    Great information. Just to clarify, the ngto_options table may be named something else, depending on local settings. The default, for example, would be wp_options.

    Thread Starter j893

    (@j893)

    11 years, 5 months ago

    Yes, that’s correct. Good catch. Thanks. I meant to change that to make it generic like “wp_options” etc….but it was 4am in the morning… 😉

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘TinyMCE Visual Editor not Working After Upgrading WordPress? READ THIS!!’ is closed to new replies.