It’s hard to believe that since the initial release of TinyMCE 5.0, TinyMCE has had 50 updates. We’ve introduced exciting new features like Real-time collaboration, PDF Export, and improvements to PowerPaste, Comments and Mentions – all to help developers empower their users to create content in ways they never thought possible.
Now, we’re pleased to introduce TinyMCE 6.0, the next step towards a new era of rich text editing.
Released first to the community on March 3 and generally available to Cloud and Self-hosted subscribers on April 6, TinyMCE 6.0 brings with it several modernizations and improvements. Possibly the most exciting change is that it opens the door for it to be used in even more projects than ever before. Curious to know why? Watch the highlights below or read on for the full details...
Quick links
TinyMCE 6.0 highlights
- New look – There’s a modern, stunning UI that can be placed directly into your app, or customized to provide tomorrow’s editing experience, today.
- MIT license – Do what you want, how you want. TinyMCE 6.0 is now licensed under MIT, which offers maximum flexibility for both open source and commercial software projects.
- New language packs – Adding Malaysian, Hindi, and Vietnamese to the library of 38 professional language translations.
- Under-the-hood improvements – DOMParser enhancements, sensible default options, and more.
- Investing in plugin development – To support their maintenance and development, Table of Contents and Enhanced Image Editing (formerly Image Tools) are now premium plugins.
- Dropping IE 11 – Out with the old, in with the new. To take advantage of modern browser capabilities, we’ve decided to drop IE 11 support.
- New docs – Moving to an easier-to-use, easier-to-search docs site.
|
Good to know: What’s in a version change? |
|
To ensure predictability and consistency for developers, TinyMCE follows Semantic Versioning:
|
What’s new in TinyMCE 6.0
Here’s a deeper dive into what you can expect with TinyMCE 6.0.
A new look
According to McKinsey, businesses that embrace design generate 32% more revenue, and 56% more shareholder returns, on average.
With TinyMCE 6.0, our Design team took a hard look at what could be done to improve TinyMCE’s default skin.
The result? A TinyMCE that helps boost your app’s appeal with its modern look, and will be just as appealing one, three, or five years from now. And exactly the same as before, it’s 100% customizable.
MIT open source license
Since our beginnings in the CMS space (and having contributed to the creation of somewhere around 40% of the web’s content), we’ve done everything we can to work towards a world where anyone, anywhere, can express themselves.
With the release of TinyMCE 6.0, our open source editor is now available under the very popular and permissive MIT license. Previously, TinyMCE 5 was available under the LGPL copyleft license which, while it didn’t have many restrictions, was lesser known to developers and legal teams, and sometimes became a barrier to adoption.
For TinyMCE 6.0, we believe the more relaxed MIT open source license empowers a new generation of developers to create apps that improve people’s lives, and make the world a better place.
New language packs
To ensure we’re delivering content creation experiences to all corners of the globe, we’ve added three new professional language packs: Hindi, Malaysian and Vietnamese.
All 38 professional language packs are translated by qualified and trusted third-party agencies, to give you the confidence that TinyMCE 6.0 is understandable and easy to use in the regions you serve.
Professional language packs are available to all Cloud subscribers, as well as all paying customers.
There are also 59 community translations now available to anyone using TinyMCE 6.0. These are contributed to and maintained by people like you, and we encourage you to add any translations you create as part of your project if you are able to do so.
Under-the-hood improvements
Being a major release, TinyMCE 6.0 was an opportunity for our Engineering team to dive deep into the codebase. They’ve made some significant improvements to how things run behind the scenes, while also making life a little bit easier for developers.
Here are some highlights:
- DOMParser improvements – The DOMParser API no longer uses a custom parser, and now uses the native browser DOMParser API. By relying on the browser DOMParser, we expect DOM parsing to be more secure and more reliable as browsers evolve over time. More details on DOMParser →
- Promises instead of callbacks – Previously, several APIs reported resource loading status with success or failure callbacks. These APIs now return a Promise, with a value of either resolve or reject. This brings our codebase more in line with modern-day standards. More details on callbacks →
- Changed options – Some options and their defaults have changed, including link_default_protocol, which now defaults to https, and schema, which now defaults to html5. By using these defaults, we are ensuring that best practices are adopted in cases where developers do not specify (or are not aware of) more advanced options like these. More details on option changes →
- Six plugins moved to core – Paste, Textpattern, Noneditable, Hr, Print, and Tabfocus are now part of the TinyMCE 6.0 core and do not need to be included in the config. This should make configs easier to maintain and simplifies managing plugin interdependencies. More on plugin movements to core →
- Deprecated items removed – Several elements were previously deprecated and have been removed entirely from TinyMCE including $, addComponents, DomQuery and others. More details on deprecated items →
Investing in plugin development
Being an open source project, it’s always our aim to deliver as much as possible to the community free of charge. After all, TinyMCE is only as strong as the 1.5M+million developers, 100M+ apps, and millions of content creators that use it.
Sometimes we need to decide whether to let a feature slip and fall behind, or invest in its future and continuing benefits for people. Therefore, to ensure their continued maintenance and development, we’ve moved Image Tools (now known as Enhanced Image Editing) and Table of Contents to our premium tiers (Essentials and above).
We hope you, the community, understand this decision and can appreciate the ongoing costs to maintain and keep relevant best-in-class software.
Anyone still using TinyMCE 5 or earlier, will continue to be able to use these two plugins as part of the open source core.
Dropping Internet Explorer 11 support
It’s with heavy hearts that we bid farewell to our long-time companion, Internet Explorer 11. With the introduction of more powerful and efficient browser functions, and the steady decline in the usage (and Microsoft support) of Internet Explorer, we’ve decided to drop support for IE11, in TinyMCE 6.0.
However before finalizing this decision, we did consult with the TinyMCE community and our customers. The response was an overwhelming ‘green light’ to drop IE11 and focus on future innovations.
TinyMCE 5, which supports IE11, will continue to be supported until April 2023.
Get TinyMCE 6.0
Starting fresh
If you’re looking to add TinyMCE 6.0 to a new project or replace your old editor, setup is fast and easy.
-
Cloud
This is the easiest way to add TinyMCE to your project.
Just sign up for your free cloud API key, copy this code snippet into your app and start customizing your editor. Best of all – Cloud subscribers benefit from automatic minor version updates, so your users are always using the latest and greatest version of TinyMCE 6.0.
-
Self-hosted NPM
npm install tinymce-
Self-hosted download
Migrating from TinyMCE 5
Depending on your configuration, you may have to make some changes to your implementation of TinyMCE 5 to migrate it to TinyMCE 6.0. Our team has put together a handy Migration Guide to help guide you through this process.
Migrating to TinyMCE from another editor
If you’re interested in migrating from your existing editor to TinyMCE, our team has put together several handy guides to help guide you through the process:
- How to migrate from CKEditor to TinyMCE
- How to migrate from Quill.js to TinyMCE
- How to migrate from Slate.js to TinyMCE
- How to migrate from TipTap to TinyMCE
- Migrating from TipTap to TinyMCE: the Vue.js configuration
Share your feedback on TinyMCE 6.0
We want to hear what you have to say about TinyMCE 6.0!
Do you have feedback on this release or a bug to report? Head over to Github Discussions to share your feedback.
What’s next?
If you haven’t already, check out the release notes for the full details around TinyMCE 6.0.
And of course, keep an eye out later this year for more releases, more features and more improvements to elevate your app’s content creation experience!
