Custom themes will not work in TinyMCE 4.7

[programmin]

Themes (meaning Tinymce js themes) that previously worked with TinyMCE <= 4.6 will not work in the upcoming 4.7.

For example if you have been filtering wp_editor_settings and change the array with:

 'theme' => 'myspecialtheme',
 'theme_url' => 'full url of js file'

it looks quite broken because the format of the theme.js file (generally the js/tinymce/themes/modern/theme.js) is vastly different format pre-4.7.

[SergeyBiryukov]

Related: #43862.

[programmin]

Confusingly it looks like if SCRIPT_DEBUG is TRUE it actually does work if you set a custom theme js, but on a production test site in which it references wp-includes/js/tinymce/wp-tinymce.php (which includes modern theme) it doesn't work and the option no longer overrides the modern theme.

[programmin]

The root of the problem may be that previously mce-themes were:

tinymce.ThemeManager.add('nameoftheme', function... )

and now the theme is

(function () { var modern = (function () {...})() } ) ()

Note that before the function does not immediately run... now it does meaning there is no way to tell mce php loader to not run that modern theme behavior.

[azaozz]

@programmin do you use a custom TinyMCE theme somewhere? Asking as this seems very rare :) If this is in a WP plugin, could you update the plugin to fix this issue?

[programmin]

Yes, and it looks like it can work fine, but only when turning off the $compress_scripts or $concatenate_scripts so that it doesn't output the highly optimized wp-tinymce.php while in print_tinymce_scripts(). Not optimal but that works.

[programmin]

Really a TinyMCE bug as that code is coming from their default modern theme...

​https://github.com/tinymce/tinymce/issues/4387

[azaozz]

Replying to programmin:

Really a TinyMCE bug as that code is coming from their default modern theme...

Yeah, I see.

it can work fine, but only when turning off the $compress_scripts or $concatenate_scripts...

Yes, not optimal but better than reverting to the old version imho. We can turn off concatenation "automatically" when theme_url is set in the init array. Patch coming up.

[azaozz]

In 43969.patch: disable concatenation if a custom TinyMCE theme is used (theme_url is set).

@programmin could you test this fast please, so we can add before RC :)

[programmin]

@azaozz Yes, that patch looks good and seems to do the exact same thing as my hacky filter fix. Would be awesomer to have the scripts included in wp-tinymce.php filterable or have one for the base TinyMCE though.

[azaozz]

Replying to programmin:

Would be awesomer to have the scripts included in wp-tinymce.php filterable or have one for the base TinyMCE though.

That's not possible :( wp-tinymce.js.gz (that is outputted from wp-tinymce.php) is concatenated and compressed at build time by Grunt.

[azaozz]

In 43222:

TinyMCE: switch off concatenation when a custom TinyMCE theme is used. Prevents conflict with the default theme as it loads first.

Props programmin, azaozz.
Fixes #43969.

[azaozz]

In 43224:

TinyMCE: switch off concatenation when a custom TinyMCE theme is used. Prevents conflict with the default theme as it loads first.

Props programmin, azaozz.
Merges [43222] to the 4.9 branch.
Fixes #43969.

[programmin]

Replying to azaozz:

Replying to programmin:

Would be awesomer to have the scripts included in wp-tinymce.php filterable or have one for the base TinyMCE though.

That's not possible :( wp-tinymce.js.gz (that is outputted from wp-tinymce.php) is concatenated and compressed at build time by Grunt.

Where is that compiled? Can one autobuild a copy with a replacement for "modern" theme?

[azaozz]

Replying to programmin:

Where is that compiled? Can one autobuild a copy with a replacement for "modern" theme?

Probably. Can try to adjust the build script for your plugin. Mostly here: https://core.trac.wordpress.org/browser/trunk/Gruntfile.js#L567 and https://core.trac.wordpress.org/browser/trunk/Gruntfile.js#L596.

[azaozz]

@programmin there have been few fixes to the "modern" theme since this ticket. Could you test if this works properly now even if the modern theme is already loaded so we can remove that fix from PHP :)

(As far as I can see the fix is not needed any more as the modern theme is initialized properly by tinymce.ThemeManager, but not sure if there may be other "side effects" from always loading the js file.)