APAR status
Closed as program error.
Error description
The integrated EditLive! rich text editor is updated to EditLive! Enterprise Edition version 9.0.1.13. Note: The default menu items and button layout has changed with this new EditLive update. To downgrade to the EditLive v7 button layout: - Run ConfigEngine.sh configure-wcm-ephox-editor-v7-configurati on on primary node only - Restart the server To rollback ᅠthe EditLive v7 button layout (restores the default EditLive v9 configuration): - Run ConfigEngine.sh remove-wcm-ephox-editor-v7-configuration on primary node only - Restart the server To install a custom EditLive v9 configuration: - Copy custom configuration file (editlive_config.xml.jsp) to [wps_profile_root]\PortalServer\wcm\shared\app\config\ephox (Create the \ephox folder if it doesn't already exist) - Note: Sample configurations can be found in [was_root]\PortalServer\wcm\prereq .wcm\wcm\config\templates\shared\app\config\ephox - Run ConfigEngine.sh configure-wcm-ephox-editor-custom-configur ation on primary node only - Restart the server To rollback a custom EditLive configuration (restores the default EditLive v9 configuration): - Run ConfigEngine.sh remove-wcm-ephox-editor-custom-configurat ion on primary node only - Restart the server What is the impact when future iFixes, Cumulative-Fixes are installed and/or when update-wcm is manually run? No impact, existing scenario choice will be remembered and re-applied. For custom configurations, requires that the custom configuration file is still present in: [wp_profile_root]\PortalServer\wcm\shared\app\config\ephox
Local fix
None available
Problem summary
The integrated EditLive! rich text editor is updated to EditLive! Enterprise Edition version 9.0.1.13. Note: The default menu items and button layout has changed with this new EditLive update. To downgrade to the EditLive v7 button layout: - Run ConfigEngine.sh configure-wcm-ephox-editor-v7-configurati on on primary node only - Restart the server To rollback  the EditLive v7 button layout (restores the default EditLive v9 configuration): - Run ConfigEngine.sh remove-wcm-ephox-editor-v7-configuration on primary node only - Restart the server To install a custom EditLive v9 configuration: - Copy custom configuration file (editlive_config.xml.jsp) to [wps_profile_root]\PortalServer\wcm\shared\app\config\ephox (Create the \ephox folder if it doesn't already exist) - Note: Sample configurations can be found in [was_root]\PortalServer\wcm\prereq .wcm\wcm\config\templates\shared\app\config\ephox - Run ConfigEngine.sh configure-wcm-ephox-editor-custom-configur ation on primary node only - Restart the server To rollback a custom EditLive configuration (restores the default EditLive v9 configuration): - Run ConfigEngine.sh remove-wcm-ephox-editor-custom-configurat ion on primary node only - Restart the server What is the impact when future iFixes, Cumulative-Fixes are installed and/or when update-wcm is manually run? No impact, existing scenario choice will be remembered and re-applied. For custom configurations, requires that the custom configuration file is still present in: [wp_profile_root]\PortalServer\wcm\shared\app\config\ephox
Problem conclusion
ConfigEngine tasks has been included in CF
Temporary fix
Comments
APAR Information
APAR number
PI11933
Reported component name
LOTUS WEB CONT
Reported component ID
5724I2900
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-02-17
Closed date
2014-04-09
Last modified date
2014-04-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
LOTUS WEB CONT
Fixed component ID
5724I2900
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU051","label":"N\/A"},"Product":{"code":"SUPPORT","label":"IBM Web Content Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB33","label":"N\/A"}}]
Document Information
Modified date:
11 December 2021