Bug: ical pull greater than 1 month may not account for 2nd dst change
Reported by dleffler | December 18th, 2012 @ 07:47 PM
If you display (request) more than one months of events (actually more than 6 months), the algorithm doesn't account for the 2nd (or more) DST changes for the times. HOWEVER, this only applies to the Upcoming Events views as all others are pretty well limited to 1 montn.
Comments and changes to this ticket
-
-
-
dleffler February 16th, 2013 @ 02:55 AM
- Milestone changed from “2.2.0alpha2” to “2.2.0alpha3”
-
dleffler March 2nd, 2013 @ 09:45 PM
- Milestone changed from “2.2.0alpha3” to “2.2.0beta1”
-
dleffler March 15th, 2013 @ 01:25 AM
There's a possibility this was fixed with the recent update to the pull external events code...
-
dleffler March 16th, 2013 @ 03:27 AM
- Milestone changed from “2.2.0beta1” to “2.2.0beta2”
-
dleffler March 29th, 2013 @ 07:59 PM
- Milestone changed from “2.2.0beta2” to “2.2.0beta3”
-
dleffler April 20th, 2013 @ 10:17 AM
- Milestone changed from “2.2.0beta3” to “2.2.0release-candidate”
-
dleffler May 1st, 2013 @ 10:22 AM
- Milestone changed from “2.2.0release-candidate” to “2.2.1”
-
-
dleffler November 19th, 2013 @ 01:57 PM
- Tag changed from “calendar” to “calendar, events”
-
-
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
dleffler
expNinja