Portal Express, Version 6.0
Rich text editor
Use the rich text editor to edit documents.
The default document editor included in IBM® WebSphere® Portal Express is the rich text editor. This lightweight editor provides many widely used functions typically available in a productivity application of its type, such as editing and saving documents.
When using the rich text editor, the default key sequences are:
ctrl + shift + M Launch detached toolbar ctrl + shift + H Launch help ctrl + shift + P Launch image insert ctrl + shift + G Launch text color chooser ctrl + shift + J Launch background color chooser ctrl + shift + T Launch table insert
These key sequences are configurable by the administrator.
To configure the key sequences, edit the KeySequence.properties file located in the following directory:
- Windows:
portal_server_root/shared/app/com/ibm/wps/odc/editors
- Linux:
portal_server_root/shared/app/com/ibm/wps/odc/editors
- i5/OS:
portal_server_root/shared/app/com/ibm/wps/odc/editors
After making changes to this file, the portal server must be restarted for the changes to take effect.
While saving a rich text editor document using a Mozilla or Firefox browser, a warning window will pop up that says, Click OK to continue. Click OK to resume the saving activity and the document will be saved. This is the default behavior.
Do not click X on the warning window.
Redo and undo functions do not work on table rows and columns
When using the rich text editor and the Internet Explorer browser, if you delete a row or column from a table, then click Redo and Undo, the table appears incorrectly. This is a known limitation when using the Redo/Undo options with Internet Explorer.
Cursor moves to the left when pressing space key:
When using the rich text editor, and the system language is set to Arabic, the edit cursor jumps to the left when you press the space key. This is a known limitation when editing in Arabic.
Rich text editor is not the default document editor:
If the rich text editor is disabled as the default editor, Document Manager users must configure a browser to automatically launch an alternative editing application. When the browser is not configured to launch a local application, the user is prompted to save the file to the local computer for editing.
Pop-up blocker prevents saving documents in the rich text editor:
If you have enabled a pop-up blocker in your browser, you will not be able to save an edited document when you click the close button (X) in the rich text editor. To avoid this problem, add the portal host site to the list of sites where pop-ups are allowed before you open the document in the rich text editor.
Find/Replace:
If you edit documents using the rich text editor through the Firefox browser, you will encounter a known limitation when using the Find and Replace function. In the Find and Replace window, the option to Match whole words when searching content is not available. The option is available when using other browsers.
Recovering a file from the temporary storage space:
While you are working in the rich text editor, if the portal session closes abruptly or the browser is closed accidentally before you can publish your file into Document Manager, you can recover the file from the temporary storage space where the file is written while you are working. The temporary space is located in a path similar to this one:
app_server_root\profiles\Profile_Name\temp\WAS_Cell_Name\WebSphere_Portal\odc\RichTextEditor.war\cds\Session_Id\Filename.ort
If you need help locating your temporary space, contact the portal administrator.
the document in temporary storage will contain the unpublished content only if it is has previously been saved by clicking the Save button, or clicking the close window X in the upper-right corner and then clicking Save.
Parent topic:
Related tasks
Editing a document Specifying the default document editor Spell check a document