Implementing the TinyMCE Rich Text Editor

Introduction to TinyMCE

TinyMCE is a platform independent web based JavaScript HTML WYSIWYG Rich Text Editor.

TinyMCE Features:

  • Modern Look and Feel
  • Easy to configure menu options
  • Configurable plugins for customizable features
  • Easy and smart GUI
  • Easier table creation tools
  • Support for 3rd party plugins

TinyMCE Editor


TinyMCE implementation in Rhythmyx

In Rhythmyx 7.3, TinyMCE is an optional control (sys_TinyMCE) which is mainly implemented to replace
existing Java based sys_EditLive control for content editor. Rhythmyx integration of TinyMCE as optional
control allows having a choice between TinyMCE and EditLive controls for content editing. In addition to
TinyMCE’s core functionality Rhythmyx provides additional controls for inline content like, inline link, Image
and template which is same as that EditLive offers.

TinyMCE editor setup in Rhythmyx

Step 1: Install the latest 7.3 Patch and Workbench
Using sys_TinyMCE control requires latest 7.3 workbench tool. If the workbench is not upgraded to 7.3 version, following link can be used to upgrade the Rhythmyx tools:


Step 2: Enable the TinyMCE control on your Content Type in the Workbench

In Workbench/Content Design tab, in a content type, choose "sys_TinyMCE" as the control type.

Enabling TinyMCE in the Workbench

Step 3:  Configure Parameters as needed. 

The following field parameters can be configured as needed by using ...(elipses) of the selected TinyMCE control


TinyMCE Control Settings

Note : As shown in above screenshot,  'Allow Inline Links', 'Cleanup Broken Inline Links', and ‘Cleanup Namespaces’ are required when using the  TinyMCE Editor.  Not specifying these options will cause Inline Links to not be processed correctly.


PropertyPurposeDefault ValueNote
heightSets the height of the Rich Text field in the Content Editor350px
  • Absolute height can be configured. Eg: 200px
widthSets the width of the Rich Text field in the Content Editor100%
  • Absolute width can be configured. Eg: 600px
config_src_urlDefines configuration file to customize TinyMCE options../rx_resources/tinymce/js/config/default_config.json
  • Custom configuration files must be placed in the  ../rx_resources/tinymce/js/config/ folder. Failing to place the file in this location will result in JavaScript errors in the Content Editor.
  • A default TinyMCE configuration with sane defaults can be found in the /Rhythmyx/sys_resources/tinymce/default_config.json file.  Copying this file to the /rx_resources/tinymce/js/config/ folder is the quickest way to enable the editor.
css_fileDefines css to override the default skin of TinyMCE../rx_resources/tinymce/tinymce.css
  • Custom css theme files must be placed in the ../rx_resources/tinymce/ folder. JavaScript errors in the content editor with the TinyMCE control will occur otherwise.
  • Sample css files (tinymce.css and tinymce1.css)are provided under Rhythmyx/rx_resources/tinymce/ location.
InlineLinkSlotSystem PropertyReserved
  • Reserved by System. Do not modify.
InlineImageSlotSystem PropertyReserved
  • Reserved by System. Do not modify
InlineVariantSlotSystem PropertyReserved
  • Reserved by System. Do not modify

Step 4.  Copy the Default TinyMCE Configuration File

Similar to EditLive configuration file (elj_config.xml), TinyMCE requires at least default_config.json file in Rhythmyx/rx_resources/tinymce/js/config folder as a default configuration file. Any TinyMCE field without custom configuration file requires the default configuration file. If custom configuration file is required for a specific TinyMCE field, such configuration file can be configured in respective field in content type. In such case the default_config.json will be replaced by the configured file. Note that, if custom configuration is not required, at least empty json node ([{}]) in default_config.json file is required. In case of empty default_config.json file, the TinyMCE is loaded with all default menu and toolbar options that are shipped with Rhythmyx. 

TinyMCE Initialization

TinyMCE is typically initialized with with an init call with a set of properties defining the configuration.

The following is an example from the tinymce documentation

<script type="text/javascript" src="<yourinstallationpath>/tinymce/tinymce.min.js"></script>
plugins: [
 "advlist autolink lists link image charmap print preview hr anchor pagebreak",
 "searchreplace wordcount visualblocks visualchars code fullscreen",
 "insertdatetime media nonbreaking save table contextmenu directionality",
 "emoticons template paste textcolor colorpicker textpattern imagetools"
toolbar1:"insertfile undo redo | styleselect | bold italic | alignleft aligncenter alignright alignjustify | bullist numlist outdent indent | link image",
toolbar2:"print preview media | forecolor backcolor emoticons",
templates: [
 {title:'Test template 1', content:'Test 1'},
 {title:'Test template 2', content:'Test 2'}

Rhythmyx initializes TinyMCE in a slightly different fashion that relies on the default_config.json configuration file.  The product implementation of TinyMCE also allows for some of the properties to be defined as a control parameter from the content editor field definition in Workbench.    General TinyMCE options can be overridden or specified by using the default_config.json file (or other if config_src_url). The default options are shown below.  On upgrade,  end users should check the Patch or Release Documentation for any special instructions related to new or deprecated configuration options. 

property name

Rhythmyx default




Mechanism Rhythmyx uses to place tinymce in editor. Do not override.



set automatically by editor control based upon field visibility



Can be specified in config json file to add css for the configuration entry.  Could be used to add role specific css.  See role configuration.



default user css set from control properties for editor in workbench.  Default as specified unless changed in control.  Do not change in json config.



system css for tinymce.  Do not override.






System value.  Do not override.



Allow all elements and attributes by default.  Care should be taken if overriding this value.  It may strip out more elements and attributes than expected and break content.  In particular elements and attributes used for Rhythmyx internal links, images, and templates should not be disallowed.





["advlist autolink lists link charmap print preview hr anchor pagebreak",

       "searchreplace wordcount visualblocks visualchars code fullscreen",

       "insertdatetime media nonbreaking save table contextmenu directionality",

       "emoticons template paste textcolor",

       "noneditable rxinline"]

List of enabled plugins.  all plugins should be in rx_resources\tinymce\js\tinymce\plugins folder and should contain plugin.js and plugin.min.js files.  Currently only plugin.js is used but this may change in the future.  If only plugin.min.js is available this can be copied to create plugin.js.

noneditable and rxinline are required for proper functionality of rhythmyx inline templates, links, and images.

If this property needs updating all required plugins need to be specified.  The plugins value in  rx_resources\tinymce\js\tinymce_init.js can be used as a basis


"insertfile undo redo | styleselect | bold italic | alignleft aligncenter alignright alignjustify |  bullist numlist outdent indent | link | print preview media | forecolor backcolor emoticons | rxinlinelink rxinlinetemplate rxinlineimage"

If this property needs updating all toolbars need to be specified.  The toolbars value in the system file rx_resources\tinymce\js\tinymce_init.js can be used as a basis.  This default  may change with new updates if we add new plugins to the product.









defaults set from editor control properties. Do not change in json config.



defaults set from editor control properties. Do not change in json config.
























System.  no longer used by noneditable plugin, will be removed.

Any of the above properties may be updated or added to the rx_resources\tinymce\js\config\default_config.json to specify initialization options.   The configuration file currently uses the JSON file format.  The format is different than that used by other TinyMCE implementations.  Noteably, Key names must be wrapped in " characters.

For example:


"image_advtab": true


    image_advtab: true


More Information