Issue 2154: Events with timezone shown on wrong day on month view
Status:  Released
Owner: ----
Closed:  Jun 2014
Reported by m...@core7.eu, May 27, 2014
The fiddle:
http://jsfiddle.net/z4dGj/1/

The event startdate is set so it includes timezone information:
moment.parseZone('2014-05-30T10:00:00+02:00').tz('Europe/Berlin')
+02:00 equals Europe/Berlin for this date, but for calculations including DST-awareness i set the whole timezone.

On the week/day agenda views the event correctly appears on May 30th, however on the month view all such events are offset to appear on the previous day, the time being correct (10am)

the fiddle is set to timezone:'local', but the shifting into the past also happens with timezone:'Europe/Berlin' (and actually in that case the time is also wrong, showing the event at 8am)

I tested it on the current v2 too, same behavior.
May 27, 2014
Project Member #1 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Reproducing
Labels: milestone-date Type-Bug
May 29, 2014
Project Member #2 adamrs...@gmail.com
I have fixed this issue in the latest commits of the v2 branch:
https://github.com/arshaw/fullcalendar/commits/v2

SIDENOTE:
If you decide to use a custom timezone in combination with the .tz() method to force a timezone on your moments, you might encounter another issue. when you drag an event to a different day or call the `updateEvent` method, the timezone info for the event will be erased. This is a "feature" because fullcalendar thinks that because the date is not local/utc, it won't know how to recalculate the timezone, so it makes it ambiguously-zoned. It doesn't know that moment-timezone knows how to make the tzo recalculation. This problem will be solved with more robust moment-timezone support, which you can open up another issue for if you want.
Status: Implemented
Jun 2, 2014
Project Member #3 adamrs...@gmail.com
version 2 has been released with this change.
http://blog.arshaw.com/1/post/2014/06/fullcalendar-2-released.html
Status: Released