-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.2.0, 7.19.30, 9.2.6, 9.2.7, 8.5.25
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
The Date Lozenge feature, which displays dates according to the user's local language settings, is expected to show the date format based on each user's settings. However, the date format is changing based on the last user's language settings who edited the page, affecting how other users see the date. This is observed only in Page edit mode.
- Date format under General Configuration: MMM dd, yyyy.
- Collaborative editing : ON
Steps to Reproduce
- Create a test page and add the Date macro with a user whose local language is set to English (US). The expected date format is MMM-dd-YYYY (note: there is another bug affecting this, see CONFSERVER-96006, but it can be ignored for this case).
- Add a few test users, Usera and Userb.
- Change Usera's local language setting under Profile to čeština (Česko).
- Edit something on the page and save it. The date will display in dd.m.yyyy (example: 24. 9. 2025) format for Usera.
- Log in as a user with the local language set to English (US) again and observe that the date also displays in čeština (Česko) instead of English.
- Log in as Userb, set the local language to Deutsch. The date will display as dd.mm.yyyy (example: 24. 09. 2025).
- Refresh the page with a user login having English (US), and the date lozenge will change to Deutsch in edit mode.
- The date will show according to the local lozenge only in Page view mode; however, in page edit mode, the date lozenge will be changed to the last updated user's local language setting.
Screen Recording 2025-09-02 at 3.03.11 PM.mov
Expected Results
The Date Lozenge should display according to the individual user's local language settings.
Actual Results
The date lozenge changes based on the last updated user's local language settings.
For example, the date is shown in čeština (Česko) for a user whose profile is set to English (US).
Workaround
"Currently there is no known workaround for this behavior. A workaround will be added here when available.".