WordPress Developers Take Note: TinyMCE 4.0 Merged Into Core

Andrew Ozz who is responsible for maintaining TinyMCE in WordPress has announced that TinyMCE 4.0 has been merged into core. The upgrade contains a number of changes including:

  • New UI and UI API.
  • New theme.
  • Revamped events system/API.
  • Better code quality, readability and build process.
  • Lots of (inline) documentation.
  • Overall improvements everywhere
TinyMCE 4.0 In Development version of WP
TinyMCE 4.0 In Development version of WP

All of the default TinyMCE plugins as well as the custom plugins used by WordPress have been upgraded to be compatible with 4.0. Since there are a lot of API changes, plugin developers are strongly encouraged to update their plugins to make sure they are compatible with 4.0 and then test them against WordPress Trunk.

Andrew Ozz listed three groups of general TinyMCE plugins that are added by WordPress Plugins.

  • A custom plugin created specifically for the WordPress plugin. If you’ve developed this kind of plugin, please see the 3.x to 4.0 migration guide and the 4.0 API documentation.
  • WordPress plugins that add third-party or default TinyMCE plugins would (of course) need to be updated to include the 4.0 version of the plugin. The PHP global $tinymce_version can be used to determine which plugin to load.
  • Mini-plugins that only add a button to the toolbar. This works pretty much the same. It is advisable to update to use the ‘dashicons’ icon font instead of image icon.

TinyMCE 4.0 IconsAfter upgrading to the bleeding edge version of WordPress 3.9 to compare the visual editor with WordPress 3.8, I immediately noticed that the Pull Quotes icon image that’s added to the visual editor disappeared. While the place holder is still there and the button functions normally, the icon image is gone. There are two other plugins that have added custom icon images to the visual editor and those work just fine. However, since they are not using SVG images or Dashicons, the experience is not consistent with the rest of the interface.

If you’re the author of a plugin that modifies or changes the behavior of TinyMCE, now is the time to test it against the trunk of WordPress so users don’t encounter unexpected changes when they upgrade to WordPress 3.9.

9 Comments


  1. It’s exciting to know these things early and be involved in the process.
    I saw Andrew’s post over the weekend and immediately had checked for one of my plugins. Turns out there is a little bug with the tooltips that are added, so I could immediately open a ticket on Trac.
    Basically no excuse for plugin developers who wait until after April 15 (release date of WP 3.9) to see whether or not their plugin still does what it says on the label…

    Report


  2. I might be wrong, but I think the image of the editor displayed above is the old version of TinyMCE. The new one looks different on the homepage: http://www.tinymce.com/. Because of that, I’ve been wondering if the new version has actually been offered to the general public through the Automatic Updates of the Beta Version, or will come in the future.

    Report


    1. It’s not entirely clear from the posts on the subject, but it has been added to Core as in development version. If you go to trunk via either SVN or Git, you will notice that it has been added. From WordPress 3.9 onwards the rest of the world will have the pleasure to see it too :)

      Report



  3. Great post – thank you!

    I’ve got a WordPress plugin which adds a button to the TinyMCE WYSIWYG editor.

    In WordPress 3.9-Alpha the button no longer displays and it prevents the rest of the WYSIWYG buttons from displaying.

    Does anyone have some advice about where might be the best place to start looking in the plugins code to make it play nicely with the new version of TinyMCE?

    I greatly appreciate it.

    Cheers :)

    Report


Comments are closed.