Add a rich text element to a template

Add a rich text element to a template

We add a rich text element to an authoring template when we want a section of HTML to be used by a set of items using the same authoring template and we want the content authors to use a rich text editor to create and edit the HTML.

Open or create an authoring template.

Click Manage Elements .

Select rich text as the element type.

Enter a name. Do not use double-byte and non-ASCII characters.

Enter a display title to use as the title of the element displayed in indexes and forms.

If we have created a text provider plug-in for a multi-locale site, we can also select the text provider and enter a key to look up a string from the selected text provider. The text provider displays a different display title for each language it has been configured for. The text entered in the Display Title field is only used if an appropriate display title is not available from the selected text provider, or if the text provider is not available.

Click OK. The rich text element is added to the form.

Go to the Default Content tab.

Go to the rich text element we added.

Enter text in the rich text field, or do nothing if we want the content creators to enter text in the rich text field.

Click
to open the display properties of the element. This is where we define how the element is displayed on the item form.

To display the element as a required field select Identify this as a required field.

To hide a field on the content form from all users select Hide field. Specify a default value if the field is a required field.
Administrators and managers can choose to display hidden fields and elements in an item by clicking Show hidden fields.

Type the number of characters to use in Field Width to set the size of the displayed field. If we leave this blank, the default field size is used.

Type a number into the maximum or minimum characters or words fields to set limits on the number of characters or words a user can enter in a field.

We can edit the default behavior of rich text elements.

Use stylesheet, hide fonts/size/color

Select this option if we want the text style to be determined by a style sheet. Content creators will not be able to edit text properties such as fonts style, text size and text color.

Limit image picker to library images

Select this to prevent content creators from inserting images from the file system. They will only be able to select images stored as image components.

Disable source mode

Select this to prevent content creators from viewing the rich text editor in source mode.

Filter active content on save

Select this to prevent users from saving active content, such as scripts, in the rich text element.

Select the users or groups to grant edit access to a field or element by clicking Add Editors.

Select the users or groups to grant view access to a field or element by clicking Add Viewers.

Type field-specific help into Field help text. This displays with the element in the content form.
If we have created a text provider plug-in for a multi-locale site, we can also select the text provider and enter a key to look up a string from the selected text provider. The text provider displays a different help text for each language it has been configured for. The text entered in the Field help field will then only be used if an appropriate help text is not available from the selected text provider, or if the text provider is not available.

We can also select to use either the default rich text editor of the authoring portlet, or a third-party rich text editor as the rich text editor for a rich text element:

Portlet default editor

If selected, the default rich text editor of the current authoring portlet is used. If the default editor is not available, the standard rich text editor is used.

Custom

Select Custom allows us to use a 3rd-party rich text editor as the default editor. Before using a compatible third-party rich text editor, we should read the installation and configuration instructions of the third-party rich text editor. These should include instructions for enabling the third-party rich text editor to be used in a Web Content Manager solution.
When configuring a third-party rich text editor, we need to copy a JSP file supplied by the third-party rich text editor. This is used to launch the third-party rich text editor. You enter the name of this JSP file in the Rich Text Options section of the authoring portlet configuration.
If the third-party rich text editor is not available, the default rich text editor of the authoring portlet is used. If the default editor is not available, the standard rich text editor is used.
JSP files are stored within a web application that runs on the portal. To reference a JSP file in another web application, use the following path: contextPath;jspPath. For example: /wps/customapplication;/jsp/jspFilename.jsp.
A dynamic context path value can be defined by adding a token to the context path that corresponds to a key and value pair to the WCM configuration service environment provider. When this key is used as the token in the jsp value field, it is replaced dynamically at render time. For example: [my.custom.key];myfile where my.custom.key is a constant within the WCM configuration service.

Save the authoring template.

Parent Use a rich text element