Joffrey JAFFEUX f0ef307d2d FIX: topic timer offset applied two times ... timezone offset was calculated and sent from browser to server, it would be applied on utc time generated from '2013-11-22 5:00' format for example and then sent back to browser which would display it thinking it's UTC time using `moment(utc time)` when it's in fact an UTC time we have offseted with the initial user timezone. This is impossible to automatically test in the current app state. Easiest reproduction is in live browser after setting your timezone to `America/New_York`, when setting a topic timer to later_today, after save, the time under the topic should be off to something roughly equal +1/-1 hour to your timezone offset.		2017-12-07 14:42:58 +01:00
..
assets	FIX: topic timer offset applied two times	2017-12-07 14:42:58 +01:00
controllers	FIX: topic timer offset applied two times	2017-12-07 14:42:58 +01:00
helpers	FEATURE: omit images from og and twitter description tags	2017-11-28 21:34:02 +01:00
jobs	FEATURE: Replace SimpleRSS with Ruby RSS module (#5311)	2017-12-06 10:45:09 +11:00
mailers	FIX: correct use of invitee vs inviter in email templates	2017-12-04 14:09:48 +05:30
models	FIX: topic timer offset applied two times	2017-12-07 14:42:58 +01:00
serializers	Merge pull request #5385 from techAPJ/search-logs-improvements	2017-12-01 12:08:38 +05:30
services	REFACTOR: Track manual locked user levels separately from groups	2017-11-27 11:23:44 -05:00
views	FEATURE: omit images from og and twitter description tags	2017-11-28 21:34:02 +01:00