View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0001243mantisbtbugtrackerpublic2001-11-28 15:292008-09-01 13:40
Reporterprescience Assigned Tograngeway  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionduplicate 
Summary0001243: Have client side times
Description

Right now all times are stored as server time. This means if you are in CST but the server is in PST then everything is PST (offset 3 hours). This can get more confusing if you are in Eurpoe or Asia.

To remedy this users could mark what timezone they are in and have times displayed localy. This code might get tricky with Daylight savings.

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
duplicate of 0001139 closedachumakov [all lang] date localisation 
related to 0006424 closeddregad Allow for per-user timezone setup 

Activities

songmaster

songmaster

2002-07-23 15:35

reporter   ~0003015

I have implemented per-user timezone settings in 0.17.3, if anyone's interested - email me anjohnson_at_iee.org for a patch file.

The gory details: I added a timezone column to the mantis_user_pref_table with all the necessary editing stuff in the accountprefs* pages, then in login_cookie_check() I set the TZ environment variable with the value of the user's preference, which causes all subsequent PHP date/time conversions to use the selected timezone.

On Unix/Linux the list of known timezones can be discovered from the zoneinfo files, usually in /usr/share/zoneinfo or /usr/share/lib/zoneinfo (location configurable), but I have also allowed this to be overridden with a config setting. My implementation assumes that the values you set TZ to are also suitable for presentation to the user, which is true on Unix/Linux, unsure on other OSs.
pmcconaghy

pmcconaghy

2005-02-01 00:22

reporter   ~0009155

Last edited: 2005-02-01 00:23

Would be useful for us - server timezone is -8, office timezone is +11, everyone complains that the times/dates are wrong!
grangeway

grangeway

2006-04-17 11:35

reporter   ~0012537

Hello,

Tidying this into a duplicate of issue 0001139 (which deals with date localisation - I think we can safely treat that as date & time)

Paul