We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time in the timestamps on the left channels panel will not respect time format chosen by user if language differs from selected in Administration.
Left sidebar has 24-hour clock for channel messages (you need Extended type of Display selected to see timestamps).
Despite user had set 24-hour clock, timestamps still show time as 12-hours clock (e.g. 3:44 PM instead of 15:44)
Version of Rocket.Chat Server: 4.5.4 Operating System: CentOS Linux release 7.9.2009 (Core) Deployment Method: yum + src Number of Running Instances: 1 DB Replicaset Oplog: NodeJS Version: v14.0.0 MongoDB Version: 4.4.13 / wiredTiger (oplog Enabled) Proxy: nginx/1.20.1 Firewalls involved: iptables, ACCEPT ALL
Video demo: https://user-images.githubusercontent.com/2260980/161399572-7bbdf1fe-37d7-41af-8765-305d848f4846.mp4
-
The text was updated successfully, but these errors were encountered:
maybe relevant to #20386
Sorry, something went wrong.
No branches or pull requests
Description:
Time in the timestamps on the left channels panel will not respect time format chosen by user if language differs from selected in Administration.
Steps to reproduce:
Expected behavior:
Left sidebar has 24-hour clock for channel messages (you need Extended type of Display selected to see timestamps).
Actual behavior:
Despite user had set 24-hour clock, timestamps still show time as 12-hours clock (e.g. 3:44 PM instead of 15:44)
Server Setup Information:
Version of Rocket.Chat Server: 4.5.4
Operating System: CentOS Linux release 7.9.2009 (Core)
Deployment Method: yum + src
Number of Running Instances: 1
DB Replicaset Oplog:
NodeJS Version: v14.0.0
MongoDB Version: 4.4.13 / wiredTiger (oplog Enabled)
Proxy: nginx/1.20.1
Firewalls involved: iptables, ACCEPT ALL
Client Setup Information
Additional context
Video demo: https://user-images.githubusercontent.com/2260980/161399572-7bbdf1fe-37d7-41af-8765-305d848f4846.mp4
Relevant logs:
-
The text was updated successfully, but these errors were encountered: