Specify Editor Version & Plugins
Specifying the TinyMCE Editor Version from Tiny Cloud
The example below shows the default way to load TinyMCE 7 from Tiny Cloud. This URL ensures the most recent and verified version of TinyMCE is used.
<script src="https://cdn.tiny.cloud/1/no-api-key/tinymce/7/tinymce.min.js" referrerpolicy="origin"></script>
To load a specific version of TinyMCE 7 other than the latest release, replace the 7
in the URL with the desired version. For example, to load a minor version such as TinyMCE 7.1
, use the following URL:
<script src="https://cdn.tiny.cloud/1/no-api-key/tinymce/7.1/tinymce.min.js" referrerpolicy="origin"></script>
To load a specific patch version, replace the 7
in the URL with the desired patch version. For example, to load TinyMCE 7.1.2
, use the following URL:
<script src="https://cdn.tiny.cloud/1/no-api-key/tinymce/7.1.2/tinymce.min.js" referrerpolicy="origin"></script>
Replace 'no-api-key' with your own API key. |
Difference between using TinyMCE 7, 7-Testing, and 7-Dev Release Channels
All Tiny Cloud channels are based on the TinyMCE Enterprise version.
|
Choose from the 7
, 7-testing
, or 7-dev
release channels to load the latest version of TinyMCE from Tiny Cloud.
These channels are updated automatically and provide the latest TinyMCE version based on the following criteria:
7 Release Channel
This channel deploys the latest release of TinyMCE that has passed our quality assurance process. The current version of TinyMCE available through the 7
channel can be found on the Tiny Cloud TinyMCE 7 version page.
7-Testing Release Channel
This channel deploys the current release candidate for the 7
channel. The TinyMCE release candidate is undergoing quality assurance. The current version of TinyMCE available through the 7-testing
channel can be found on the Tiny Cloud TinyMCE 7-testing version page.
7-Dev Release Channel
This channel deploys nightly builds of TinyMCE, which includes unreleased changes from the TinyMCE repository.
The current version of TinyMCE available on the 7-dev
channel can be found on the Tiny Cloud TinyMCE 7-dev version page.
TinyMCE now uses main branch for nightly builds instead of develop as of TinyMCE 7.0.0 .
|
Example: Using the 7-dev
Release Channel
<script src="https://cdn.tiny.cloud/1/no-api-key/tinymce/7-dev/tinymce.min.js" referrerpolicy="origin"></script>
For more details, check out the TinyMCE editor via Tiny Cloud.
Specifying the Cloud Deployment of Plugins
When self-hosting TinyMCE, integrators have the choice to host premium plugins or load them from Tiny Cloud (a.k.a. hybrid mode). Depending on your requirements, you can use a combination of both approaches.
The cloud plugin script tag must be positioned between the TinyMCE script tag and the tinymce.init() call. For applications that bundle TinyMCE, delay the tinymce.init() call until after the cloud plugin script tag has loaded. This ensures that the cloud plugins are available when the editor is initialized.
|
Tiny offers the following configuration scripts to assist:
plugin.min.js
Standalone with No Exclusions
The plugins.min.js
script loads every premium plugin the API key is entitled to from the CDN.
<script src="https://cdn.tiny.cloud/1/api-key/tinymce/7/plugins.min.js" referrerpolicy="origin"></script>
plugins.min.js
with Exclusions for Specific Plugins
To exclude specific premium plugins from plugins.min.js
because you are self-hosting them, add the excluded plugins to the script query parameters as shown below:
<script src="https://cdn.tiny.cloud/1/api-key/tinymce/7/plugins.min.js?mentions=sdk&powerpaste=sdk" referrerpolicy="origin"></script>
Ensure that the excluded plugins' names are appended with When Tiny Cloud releases a new premium plugin, if you wish to self-host it, this script tag will need to be updated to exclude it. |
cloud-plugins.min.js
for Specific Premium Plugins from Tiny Cloud
The cloud-plugins.min.js
script allows loading of specific premium plugins from Tiny Cloud.
<script src="https://cdn.tiny.cloud/1/api-key/tinymce/7/cloud-plugins.min.js?mentions&powerpaste&advcode" referrerpolicy="origin"></script>
This approach is intended for edge cases where you self-host most premium plugins on your own servers and only need one or two from Tiny Cloud. |