Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Calendar event pages for full day event show (wrong) times #560
Comments
|
This problem keeps popping up again and again for full day events (all conferences we add to the Google calendars), e.g. most recently here: https://www.python.org/events/python-events/467/ The event is from April 3-7 and shown correctly in the Google calendar widget: |
* Make the event importer to exclude the ending day in case of a full day event * Don't create a datetime instance from a date object if an event is a full day event Fixes python#375 Fixes python#560
|
This bug still exists: https://www.python.org/events/python-events/800/ vs. http://www.pycon.org/#calendar The problem is that full day events should be displayed using times (or time zones for that matter), but just the dates, which are correctly entered into the Google calendars. |
|
IIRC, this hasn't been deployed to production yet. Could you please check it at staging.python.org? |
|
Looks fine for EuroPython on staging: https://staging.python.org/events/python-events/794/ So I guess all that needs to be done is deploy on production :-) Thanks, Berker ! |
See e.g. https://www.python.org/events/python-events/246/
This is an event for the days March 28 and 29. The calendar entry uses all day entries for this, without specifying times on each day. Yet the python.org site displays "From 28 March at 12am UTC through 30 March at 12am UTC, 2015", so it's 12 hours off.
The all day event should really only show up as "From 28 March through 29 March".
The iCal entry for the events starts with:
BEGIN:VEVENT
DTSTART;VALUE=DATE:20150328
DTEND;VALUE=DATE:20150330
DTSTAMP:20150202T092425Z
...
without timezone information.
The text was updated successfully, but these errors were encountered: