Overview
TinyMCE 5.8.1 was released for TinyMCE Enterprise and Tiny Cloud on Wednesday, May 26th, 2021. It includes TinyMCE 5.8.1 and additional changes to premium plugins. These release notes provide an overview of the changes for TinyMCE 5.8.1, including:
- Accompanying Premium Plugin changes
- General bug fixes
- Security fixes
- Upgrading to the latest version of TinyMCE 5
Note: 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.1.
Advanced Code 2.3.1
The TinyMCE 5.8.1 release includes an accompanying release of the Advanced Code premium plugin.
Advanced Code 2.3.1 includes updates to third-party dependencies, fixing a moderate severity ReDoS vulnerability.
For information on the Advanced Code plugin, see: Advanced Code plugin.
Export 1.0.1
The TinyMCE 5.8.1 release includes an accompanying release of the Export premium plugin.
Export 1.0.1 fixes an issue where content was lost in the PDF output in some cases due to a compiler issue.
For information on the Export plugin, see: Export plugin.
Tiny Drive 1.4.1
The TinyMCE 5.8.1 release includes an accompanying release of Tiny Drive.
Tiny Drive 1.4.1 fixes an issue where the skin
setting wasn’t working in standalone-mode.
For information on Tiny Drive, see: Tiny Drive.
General bug fixes
TinyMCE 5.8.1 provides fixes for the following bugs:
- An unexpected exception was thrown when switching to readonly mode and adjusting the editor width.
- Content could be lost when the
pagebreak_split_block
setting was enabled. - The
list-style-type: none;
style on nested list items was incorrectly removed when clearing formatting. - URLs were not always detected when pasting over a selection. Patch contributed by jwcooper.
- Properties on the
OpenNotification
event were incorrectly namespaced.
Security fixes
TinyMCE 5.8.1 provides fixes for the following security issues:
The Advanced Code plugin (advcode
) has been updated to include upgraded third-party dependencies to fix a moderate severity ReDoS vulnerability.
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:
-
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/
-
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
.
- For the TinyMCE Community Version, download
- Extract the downloaded
.zip
file to a temporary location. - (If required) Install the latest language packs from Get TinyMCE - Language Packages.
-
Copy customizations to the new
tinymce/
directory. Ensure that only custom changes are added the newtinymce/
directory, such as:- Custom icons packs
- Custom plugins
- Custom skins
- Custom themes
- Delete the existing
tinymce/
directory and replace with the newtinymce/
.
Note: To simplify the upgrade process to future versions of TinyMCE:
- Host the TinyMCE customizations outside of the
tinymce/
directory.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 oficons
.- Set the location of custom localization packages using
language_url
instead oflanguage
.- Set the location of custom skin packages using
skin_url
instead ofskin
.- Set the location of custom themes using
theme_url
instead oftheme
.
Was this article helpful? Yes - No
Well, that's awkward . Would you mind opening an issue or helping us out?
Thanks for the feedback!
Can't find what you're looking for? Let us know.
Except as otherwise noted, the content of this page is licensed under the Creative Commons BY-NC-SA 3.0 License, and code samples are licensed under the Apache 2.0 License.