Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-55484

Exporting a calendar changes events with no endtime into an event for the wrong day

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Deferred
    • Icon: Major Major
    • None
    • 3.1.1, 3.3
    • Calendar
    • MOODLE_31_STABLE, MOODLE_33_STABLE
    • Hide
      1. Run unit tests from the calendar/tests/lib_test.php file.
      2. As a user, set your timezone in your profile so that it is UTC+something (e.g. Australia/Perth has UTC+8).
      3. Create an event in the calendar with a date/time set in a way that in the UTC (GMT) timezone the event has different date (e.g. event starting at 6am Perth time is 22:00 UTC of the previous day). Select "Without duration".
      4. Export the calendar event into iCalendar file
      5. TEST: Check that the exported ics file has still expected date on the line DTSTART;VALUE=DATE:YYYYMMDD and the line with DTEND is one day later.
      6. TEST: Import this ics file back to Moodle calendar (not very intuitively this is done via Manage subscriptions button) and check that the event is created in the same day as the original event (the actual event start time may be different).
      Show
      Run unit tests from the calendar/tests/lib_test.php file. As a user, set your timezone in your profile so that it is UTC+something (e.g. Australia/Perth has UTC+8). Create an event in the calendar with a date/time set in a way that in the UTC (GMT) timezone the event has different date (e.g. event starting at 6am Perth time is 22:00 UTC of the previous day). Select "Without duration". Export the calendar event into iCalendar file TEST: Check that the exported ics file has still expected date on the line DTSTART;VALUE=DATE:YYYYMMDD and the line with DTEND is one day later. TEST: Import this ics file back to Moodle calendar (not very intuitively this is done via Manage subscriptions button) and check that the event is created in the same day as the original event (the actual event start time may be different).
    • 3.4 Sprint 2

      My timetzone is UTC+2

      An event with a start and stop time vom 3am to 4am (UTC+2) will be changed in an event in UTC+0 two hours earlyer:
      The following export shows, that the event is from 1am to 2am (UTC+0)

      BEGIN:VEVENT
      UID:611@
      SUMMARY:Termin 3:00 bis 4:00
      DESCRIPTION:
      CLASS:PUBLIC
      LAST-MODIFIED:20160806T125915Z
      DTSTAMP:20160806T130351Z
      DTSTART:20160807T010000Z
      DTEND:20160807T020000Z
      CATEGORIES:xxx

      I think here moodle works correct.

      The problem occurs with events that have NO stoptime.
      Example: An Event at 1 a clock (1am)
      BEGIN:VEVENT
      UID:615@xxxxx
      SUMMARY:samstag 20160806 1 uhr
      DESCRIPTION:
      CLASS:PUBLIC
      LAST-MODIFIED:20160806T142144Z
      DTSTAMP:20160806T142209Z
      DTSTART;VALUE=DATE:20160805
      DTEND;VALUE=DATE:20160806
      CATEGORIES:xxxxxxxxx
      END:VEVENT

      I think that in the moment moodle first changes the event from 20160806 1am(UTC+2) into an event 20160805 11pm(UTC+0) and than moodle makes an event for the hole day 20160805.

      I think moodle should better support events with no endtime by setting the the endtime to the same as the beginingtime.
      Moodle shoud NOT change make an event into a daliy.

        1. 0001-MDL-55484-calendar-Fix-incorrect-date-of-exported-al.patch
          7 kB

            Unassigned Unassigned
            moodleaccount A. Schenkel
            Ankit Agarwal Ankit Agarwal
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.