#519 ✓resolved
dleffler

Feature request: Allow calendar to be more forgiving of time zones

Reported by dleffler | February 2nd, 2012 @ 01:11 PM | in 2.0.9 (closed)

In 0.9x, you could reuse modules. When migrating, looks like we don't check for the 'is_original' flag and end up placing events in a different calendar (can't reuse modules in 2.0) so that they don't flow/aggregate correctly.

Comments and changes to this ticket

  • dleffler

    dleffler February 2nd, 2012 @ 01:19 PM

    • Title changed from “Bug: Migration (calendars?) might pull events into the NON-original calendar” to “Bug: Migrated calendars don't show events in month/list/week/day view”

    Actually seems that events are migrated to the correct calendar, but only shown in Administration or Headline views.

  • dleffler

    dleffler February 2nd, 2012 @ 03:45 PM

    • Title changed from “Bug: Migrated calendars don't show events in month/list/week/day view” to “Feature request: Allow calendar to be more forgiving of time zones”
    • Milestone cleared.
    • Tag changed from calendar, migration to calendar

    Actually this is a problem with the site's timezone setting. The NEW calendar and the OLD calendar, MUST have been set to the same time zone.

    We might want to make our data extraction more tolerant of the eventdate->date entry to look for an entire day instead of just the single second at the beginning of the local day.

    May also want to add some sort of conversion when switching site time zones?

    Again, most of this is moot since we should be upgrading to Calendar2 in the near future.

  • dleffler

    dleffler May 15th, 2012 @ 12:15 AM

    • State changed from “new” to “open”
  • dleffler

    dleffler May 15th, 2012 @ 02:11 AM

    Well, since we're not move to Calendar2 in the near future...we may incorporate this by getting events between startofday and endofday since we have the methods available.

  • dleffler

    dleffler July 27th, 2012 @ 08:01 PM

    • Milestone set to 2.0.9
    • Milestone order changed from “19” to “0”
  • expNinja

    expNinja August 1st, 2012 @ 01:31 PM

    • State changed from “open” to “resolved”
    • Milestone order changed from “7” to “0”

    (from [35188ed491aa67c27a5a408acea2eef8a6352d8f]) Fixes several calendar problems, such as may not be display events (we weren't passing src on old school links), now checks for entire 24 hour day to be more forgiving of timezone changes [#674 #519 state:resolved] https://github.com/exponentcms/exponent-cms/commit/35188ed491aa67c2...

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.

New-ticket 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

Shared Ticket Bins

People watching this ticket

Tags

Referenced by

Pages