Adding a rich text element to a template

You add a rich text element to an authoring template when you want a section of HTML to be used by a set of items that use the same authoring template and you want your 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 you have created a text provider plug-in for a multi-locale site, you 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 your form.
Go to the Default Content tab.
Go to the rich text element you added.
Enter text in the rich text field, or do nothing if you want your content creators to enter text in the rich text field.
Click to open the display properties of the element. This is where you define how the element is displayed on the item form.
1. To display the element as a required field select Identify this as a required field.
2. To hide a field on the content form from all users select Hide field. You must specify a default value if the field is a required field.
  Note: Administrators and managers can choose to display hidden fields and elements in an item by clicking Show hidden fields.
3. Type the number of characters to use in Field Width to set the size of the displayed field. If you leave this blank, the default field size is used.
4. 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.
5. You can edit the default behavior of rich text elements.
  Use stylesheet, hide fonts/size/color
  
  Select this option if you 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.
6. Select the users or groups you want to grant edit access to a field or element by clicking Add Editors.
7. Select the users or groups you want to grant view access to a field or element by clicking Add Viewers.
8. Type field-specific help into Field help text. This displays with the element in the content form.
  If you have created a text provider plug-in for a multi-locale site, you 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.
9. You 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
  Selecting Custom allows you to use a 3rd-party rich text editor as your default editor. Before using a compatible third-party rich text editor, you 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, you 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.
  Storing JSP Files:
  JSP files can be located:
  
  within the was_profile_root/installedApps/node-name/wcm.ear/ilwwcm.war directory of your server.
  The JSP page is also stored in the client war directory of the local rendering portlet or of the servlet or portlet that calls the JSP, if using the Web Content Manager API. For example, to render a JSP page on a local rendering portlet, you would also need to store a copy of the JSP file under was_profile_root/installedApps/node-name/PA_WCMLocalRendering.ear/ilwwcm-localrende.war
  
  within any other web application running on portal. When referencing JSP files in another web application, use the following path: contextPath;jspPath
  For example: /wps/customapplication;/jsp/editor.jsp
Save the authoring template.