|Description||Apparently, one can set a user timezone default. an user timezone AND a system timezone - this should be more clearly mentioned in the wiki (have done that on installation page/getting started). |
Maybe the tooltip in system admin could give a hint at the triple settings?
Whoever outside the US changes the system settings will have problems with the times in the db.
As I would typically assume that w2p is installed in a consistent time setting, one could argue whether changing the system timezone should not ask whether to change all other timezones as well.
Otherwise, for installers outside the US, the procedure is:
1) change system timezone
2) change user default timezone
3) change timezone for the admin account that has already been created.
feels a bit strange, especially, if no guidance is given.
BUG: Actually, the dP upgrade script has a bug: I have exactly this inconsistency - system TZ is Berlin, user default TZ and all user TZ are US timezone. So in effect, all my times BEFORE the upgrade will be identical to webserver timezone (=Berlin, OK), all my times after will have the offset created by the upgrade script - oh god, that will be fun to correct. Well - maybe not: all db times after creation time of db (see filesystem) will be wrong.
In task view, everything looks alright: if I enter 9am, the db saves 3pm but converts to 9am upon task view creation. Problem shows in the ical feed - there, 3pm is put into the feed for GMT time of task.
Correct upgrade procedure from dP: ask for TZ, set it identical for system, user default, all users (maybe also ask whether server TZ is different)