48: Time zone overhaul - Composr CMS feature tracker

ID	Project	Category	View Status	Date Submitted	Last Update

48	Composr	calendar	public	2010-04-06 10:49	2011-10-05 20:10

Reporter	Chris Graham	Assigned To	Chris Graham
Priority	normal	Severity	feature
Status	resolved	Resolution	fixed

Summary	48: Time zone overhaul
Description	1) Half hour timezones Support half-hour timezones fully. We currently only support them for site-time, not member timezone settings. This is because members have an integer field for their setting. We should change that field to ID_TEXT. This is not a huge priority because countries with half hour timezones probably are going to only have a nationally-used site not an international one (e.g. people outside India are not likely to use an Indian site). 2) Remove the current 3-way-tilting-mechanism strftime -> gmstrftime and date -> gmdate (so we no longer have to factor in a servers set time zone into account, as that makes things unnecessarily over-complex) Make the default value for the timezone option be determined by the server's timezone Make the member timezone option be for setting the site's default timezone, if JS cannot detect it and a member has not set it - it does not get taken into account if either of those have happened Update the timezone selection lists to only range between the negative and positive offset maximums we have. It is currently longer due to the need for possible compensation for adverse interactions between server/site/member setting that can exaggerate the need for compensations. 3) Show in footer Option to show the date/time in the FOOTER template (adjusted to timezone). Say it like "It's 12th February 9:32am according to your time settings." Also show next to any date/time selector. 4) Calendar events Per calendar-event, allow you to choose a timezone the time you are setting the event for. If you do not select one, the time will be shown in the viewer's own timezone. Either way Composr will say the timezone to users viewing the event. If an event is not being shown in the viewer's own timezone (it was added with a timezone that is different to their own) then disable contextual dates/times for when the date/time is written out. Things like "Yesterday" are very confusing when referring to times in another timezone (yesterday can be later today if you're working across time zones). 5) Automatic DST Less important - consider using Pear Date to select textual timezones and calculate seasonal timezone offsets (i.e DST). This re-treads area covered by '1' and some of '2', but we can do it afterwards as an even better enhancement.
Tags	Risk: Changes core website behaviour , Risk: Core rearchitecting , Risk: Large database change , Risk: Major rearchitecting , Type: Cross-cutting feature
Attach Tags	(Separate by ",")

Time estimation (hours)	12
Sponsorship open

Date Added	Member	Amount Sponsored

Date Modified	Username	Field	Change
2016-06-08 00:14	Chris Graham	Tag Renamed	Major rearchitecting => Risk: Major rearchitecting
2016-06-08 00:15	Chris Graham	Tag Renamed	Large database change => Risk: Large database change
2016-06-08 00:15	Chris Graham	Tag Renamed	Core rearchitecting => Risk: Core rearchitecting
2016-06-08 00:15	Chris Graham	Tag Renamed	Changes core website behaviour => Risk: Changes core website behaviour