Fixes are available
6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1
Recommended Updates for WebSphere Portal and Web Content Management V6.1
6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5
Fixes integrated in WebSphere Portal V7.0 Combined Cumulative Fix
6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6
7.0.0.2 Download: WebSphere Portal and WCM V7.0 fix pack 2
7.0.0.1 Download: WebSphere Portal and WCM V7.0 fix pack 1
APAR status
Closed as program error.
Error description
Problem: In enabling site cache, the locale of a rendered a date field of a workflow cmpnt is inconsistent Description: With site caching enabled, when the user renders the date field in a browser with a specific locale and then subsequently views the same workflow cmpnt date field on a secondary machine with a different browser locale, the date field is rendered in the initial browser's locale. In addition, the customer wants to be able to control the date locale by specifying a default. Analysis: The date fields of a workflow component are rendered using the clients browser locale, however in site caching we cache the date fields of a workflow cmpnt, so although the clients browser locale might have changed, until cache expiration they will still see the cached date field. Solution: Created a parameter in the WCMConfigService.properties where the customer can specify a default locale. e.g. renderer.workflowCmpnt.date.locale=en_US. If this parameter is available this date locale is used regardless of the browser locale
Local fix
Problem summary
Problem: In enabling site cache, the locale of a rendered a date field of a workflow cmpnt is inconsistent Description: With site caching enabled, when the user renders the date field in a browser with a specific locale and then subsequently views the same workflow cmpnt date field on a secondary machine with a different browser locale, the date field is rendered in the initial browser's locale. In addition, the customer wants to be able to control the date locale by specifying a default.
Problem conclusion
Analysis: The date fields of a workflow component are rendered using the clients browser locale, however in site caching we cache the date fields of a workflow cmpnt, so although the clients browser locale might have changed, until cache expiration they will still see the cached date field. Solution: Created a parameter in the WCMConfigService.properties where the customer can specify a default locale. e.g. renderer.workflowCmpnt.date.locale=en_US. If this parameter is available this date locale is used regardless of the browser locale
Temporary fix
Comments
APAR Information
APAR number
PM09042
Reported component name
LOTUS WEB CONT
Reported component ID
5724I2900
Reported release
61C
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-04
Closed date
2010-04-28
Last modified date
2010-04-28
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
R615 PSY
UP
R61A PSY
UP
R61B PSY
UP
R61C PSY
UP
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.3","Edition":"","Line of Business":{"code":null,"label":null}}]
Document Information
Modified date:
09 September 2020