tinyMceConfig

Here you will find documentation relating to the options you can add/modify in the tinyMceConfig.config file. The configuration you set here will be used by each TinyMce instance as it is initialized in Umbraco.

commands

Inside of the <commands> node you will find multiple <command> nodes. Each one of these nodes defines a icon/button that can appear on the formatting bar inside of Umbraco and the command that is triggered when it is clicked.

umbracoAlias defines a unique alias within Umbraco for the command. This alias should not contain any spaces.

icon defines the path to an image file to be used on the formatting toolbar. This image should be 16px x 16px in size.

tinyMceCommand defines the tinyMceCommand properties.

To further break this down, the value attribute is usually an empty value as most commands perform formatting tasks as opposed to returning values. The userInterface attribute takes a boolean value indicating whether or not the command has an additional UI component to display e.g. a new dialog to assist with inserting images. frontendCommand defines the name of the command to execute. This value usually matches the value of the tinyMceCommand node.

priority defines the sort order for the commands and should be sequentially incremented for each new command.

plugins

Inside of the <plugins> node you can find one or more <plugin> nodes. Each one of these nodes defines a plugin which extends the functionality of TinyMce. Below you will find the standard plugins configured in a clean install of Umbraco v6.x.

Control characters:

Rules with this name will be applied to all elements defined after this rule. So @[attr1|attr2] will enable attr1 and attr2 for all elements, but element1,@[attr1|attr2],element2,element3 will enable attr1 and attr2 only for element2 and element3.

If applied in extended_valid_elements, it is only effective for the elements in the extended_valid_elements list.

,

Separates element chunk definitions.

/

Separates element synonymous. The first element is the one that will be output.

|

Separates attribute definitions.

[

Starts a new attribute list for an element definition.

]

Ends an attribute list for an element definition.

!

Makes attributes required. If none of the required attributes are set, the element will be removed. For example, "!href".

=

Makes the attribute default to the specified value. For example, "target=_blank"

:

Forces the attribute to the specified value. For example, "border:0"

<

Verifies the value of an attribute (only the listed values are allowed). For example, "target<_blank?_self"

?

Separates attribute verification values. See above.

+

Makes the element open if no child nodes exists. For example, "+a".

-

Enables removal of empty elements such as <strong />. For example, "-strong".

#

Enables padding of empty elements. This will pad with &nbsp; if they are empty. For example, "#p".

invalidElements

This option should contain a comma separated list of element names to exclude from the saved content. Elements in this list will be removed when your content is saved.

<invalidElements>font</invalidElements>

extendedValidElements

Extended valid elements is a configuration option of TinyMCE that is normally used to apply extensions to the validElements setting of TinyMCE. This configuration setting is however not available in the current implementation of TinyMCE in Umbraco CMS.

Our.umbraco.com is the community mothership for Umbraco, the open source asp.net cms. With a friendly forum for all your questions, a comprehensive documentation and a ton of packages from the community.
This site is running
Umbraco version 7.13.1