Reserved authoring portlet
When working with the web content viewer or Web content pages, some scenarios involve web content authoring tasks accomplished with authoring tools components. Such authoring tasks are performed through a special instance of the authoring portlet reserved specifically for these tasks, installed on a page hidden from the page navigation available to typical users.
Tasks using the reserved authoring portlet include...
- Selecting a web content folder when editing the properties of a web content page
- Configuring the web content viewer, such as selecting the content item to display
- Performing inline editing using authoring tools components rendered in the web content viewer
Typically authoring tasks are performed in a separate window that opens from the current page, but we can configure the behavior of authoring tools components to redirect users to the hidden page containing the reserved authoring portlet.
Ensure the availability of the reserved authoring portlet
If either the authoring portlet instance or the hidden portal page are not available, or if the user lacks the permission to access either of them, the authoring tasks requiring the reserved authoring portlet will fail, causing web content pages and the web content viewer to be unusable. Exercise caution when administering the reserved authoring portlet and the hidden portal page.
Users must have the User role on the hidden portal page and the reserved authoring portlet. The reserved authoring portlet must be the only portlet located on the hidden portal page.
The unique name of the hidden portal page must be...
com.ibm.wps.hiddenpage.wcm.Authoring_Portlet
The unique name of the portlet window of the authoring portlet instance on the hidden portal page must be...
com.ibm.wps.hiddenpage.wcm.control.Authoring_Portlet
Availability problems related to the reserved authoring portlet or the hidden portal page are usually identified by the following symptoms:
- The SystemOut.log file for the portal server contains error messages referencing the authoring portlet or hidden page. For example:
- EJPDB0124E: The specified string [com.ibm.wps.hiddenpage.wcm.Authoring_Portlet] can neither be deserialized as an object ID nor resolved as a unique name.
- EJPDB0124E: The specified string [com.ibm.wps.hiddenpage.wcm.control.Authoring_Portlet] can neither be deserialized as an object ID nor resolved as a unique name.
- When a separate window is launched from the current page to perform the authoring task, the new window displays the following message:
Error 400: EJPPH0006E: The resolution of a URI failed. Refer to the stack trace for more detailed information.
- When a separate window is launched from the current page to perform the authoring task, the new window is empty.
- When the user is redirected to another portal page to perform the authoring task, the user is redirected to the default portal page instead of the page containing the reserved portlet.
- When the user is redirected to another portal page to perform the authoring task, the user is redirected to an empty page.
If any of these problems occur, verify the conditions for proper operation of the reserved authoring portlet and hidden portlet page are fully implemented.
If the reserved authoring portlet or the hidden portlet page are removed inadvertently, we can deploy them again using the action-install-wcm-hidden-authoring configuration task.
See
Parent Web Content Manager