TinyMCE 5.8.2

Overview

TinyMCE 5.8.2 was released for TinyMCE Enterprise and Tiny Cloud on Wednesday, June 30th, 2021. It includes TinyMCE 5.8.2 and additional changes to premium plugins. These release notes provide an overview of the changes for TinyMCE 5.8.2, including:

This is the Tiny Cloud and TinyMCE Enterprise release notes. For information on the latest community version of TinyMCE, see: TinyMCE Changelog.

Accompanying Premium Plugin changes

The following premium plugin updates were released alongside TinyMCE 5.8.2.

Export 1.0.2

The TinyMCE 5.8.2 release includes an accompanying release of the Export premium plugin.

Export 1.0.2 provides the following bug fixes:

  • The client-side PDF exporter would fail to export when a circular reference was present during JSON serialization.

For information on the Export plugin, see: Export plugin.

PowerPaste 5.5.1

The TinyMCE 5.8.2 release includes an accompanying release of the PowerPaste premium plugin.

PowerPaste 5.5.1 provides the following bug fixes:

  • Fixed a performance issue when pasting Google Docs content.

  • Fixed indented text pasted from Google Docs unable to be outdented.

  • Pasted images that failed to be converted to a blob would cause an uncaught exception and lock up the editor.

For information on the PowerPaste plugin, see: PowerPaste plugin.

Spell Checker Pro 2.3.2

The TinyMCE 5.8.2 release includes an accompanying release of the Spell Checker Pro premium plugin.

Spell Checker Pro 2.3.2 provides the following bug fixes:

  • Entering hasOwnProperty into the editor was throwing exceptions.

For information on the Spell Checker Pro plugin, see: Spell Checker Pro plugin.

General bug fixes

TinyMCE 5.8.2 provides fixes for the following bugs:

  • Fixed an issue when pasting cells from tables containing colgroups into tables without colgroups.

  • Fixed an issue that could cause an invalid toolbar button state when multiple inline editors were on a single page.

Upgrading to the latest version of TinyMCE 5

The procedure for upgrading to the latest version of TinyMCE 5 depends on the deployment type.

Upgrading Tiny Cloud

Tiny Cloud provides the latest enterprise version of TinyMCE. For information on configuring Tiny Cloud, see: the Cloud deployment guide.

Upgrading TinyMCE Self-hosted manually

To upgrade to TinyMCE 5.10 using a manually downloaded package:

  1. Backup the tinymce/ directory so any customizations can be restored after the upgrade.

    Customizations for TinyMCE are typically stored in the following directories:

    tinymce/
├── icons/
├── langs/
├── plugins/
├── skins/
│   ├── content/
│   └── ui/
└── themes/

  2. Download the latest version of TinyMCE.

    • For the TinyMCE Community Version, download tinymce_<VERSION>.zip from Get TinyMCE - Self-hosted releases, where <VERSION> is the latest version of TinyMCE.

    • For the TinyMCE Enterprise Version, download the TinyMCE Enterprise Bundle from Tiny Account > Downloads. The downloaded file will be named enterprise_latest.zip.

  3. Extract the downloaded .zip file to a temporary location.

  4. (If required) Install the latest language packs from Get TinyMCE - Language Packages.

  5. Copy customizations to the new tinymce/ directory. Ensure that only custom changes are added the new tinymce/ directory, such as:

    • Custom icons packs

    • Custom plugins

    • Custom skins

    • Custom themes

  6. Delete the existing tinymce/ directory and replace with the new tinymce/.

To simplify the upgrade process to future versions of TinyMCE:

  1. Host the TinyMCE customizations outside of the tinymce/ directory.

  2. Update your TinyMCE configuration as required:

    • Set the location of content CSS customizations using content_css.

    • Set the location of custom plugins using external_plugins.

    • Set the location of custom icon packages using icons_url instead of icons.

    • Set the location of custom localization packages using language_url instead of language.

    • Set the location of custom skin packages using skin_url instead of skin.

    • Set the location of custom themes using theme_url instead of theme.