+

Search Tips   |   Advanced Search

Define editor options

We configure Web Content Manager to use different editors for rich text and HTML fields.


Rich text editor

    Default
    Use the default JavaScript editor. This does not require a working Java runtime environment on the client computer.

    EditLive! JavaScript Editor
    Use the EditLive! JavaScript editor. This does not require a working Java runtime environment on the client computer. Browser pop-ups must be enabled to use this editor.

    EditLive! Java Editor
    Use the EditLive! Java Editor. This requires a working Java runtime environment on the client computer. Browser pop-ups must be enabled to use this editor.

    Custom

    Select Custom allows us to use a third-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 file 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 standard rich text editor is used.


HTML editor

    Default
    Use the default HTML editor.

    Custom

    Select Custom allows us to use a third-party HTML editor as the default editor. Before using a compatible third-party HTML editor, we should read the installation and configuration instructions of the third-party HTML editor. These should include instructions for enabling the third-party HTML editor to be used in a Web Content Manager solution.

    When configuring a third-party HTML editor, we need to copy a JSP file supplied by the third-party HTML editor. This file is used to launch the third-party HTML editor. You enter the name of this JSP file in the HTML Options section of the authoring portlet configuration.

    If the third-party HTML editor is not available the default HTML 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.


Parent Authoring portlet settings