XMLWordPrintable

Details

    • MOODLE_20_STABLE, MOODLE_23_STABLE
    • MOODLE_23_STABLE
    • MDL-22895-master
    • Easy
    • Hide
      1. Get ready, this can take a while
      2. Create a complete range of different Calender events including atleast
        *site events (sitepages->calendar->new event->type>site)
        *site events that are repeated (use the repeat setting while creating a calendar event)
        *user events (sitepages->calendar->new event->type->user)
        *group events
        *course events (gotto a course-> add calendar block-> click on month name->new event)
        *Course events with images in description
        *course events that are repeated (use the repeat setting while creating a calendar event)
        *activity events. (Activity events are automatically created when you create a activity with due dates)
      3. Backup the course, with default option.
      4. Make sure you see the check box "include calender events" during the backup and restore procedures.
      5. Just to be extra safe make sure course and activity folder in the backups have calendar.xml with respective events data
      6. Restore the course as the following
      • on an existing course on same site
      • on a new course on same site
      • on an existing course on a different site
      • on a new course on a different site
      1. Make sure in each case all events except site events and user events are transfered properly. (We are not backing up site events and user events)
      2. Make sure repeated events are properly restored.
      3. Make sure events with images are restored properly and images are present in the restored events.
      4. Also cross check the database to make sure the newly created events are associated with correct ids of activity, user and group.i.e they are tied to the new ids not the old ones
      5. run this test on atleast more than one type of DB
      Show
      Get ready, this can take a while Create a complete range of different Calender events including atleast *site events (sitepages->calendar->new event->type>site) *site events that are repeated (use the repeat setting while creating a calendar event) *user events (sitepages->calendar->new event->type->user) *group events *course events (gotto a course-> add calendar block-> click on month name->new event) *Course events with images in description *course events that are repeated (use the repeat setting while creating a calendar event) *activity events. (Activity events are automatically created when you create a activity with due dates) Backup the course, with default option. Make sure you see the check box "include calender events" during the backup and restore procedures. Just to be extra safe make sure course and activity folder in the backups have calendar.xml with respective events data Restore the course as the following on an existing course on same site on a new course on same site on an existing course on a different site on a new course on a different site Make sure in each case all events except site events and user events are transfered properly. (We are not backing up site events and user events) Make sure repeated events are properly restored. Make sure events with images are restored properly and images are present in the restored events. Also cross check the database to make sure the newly created events are associated with correct ids of activity, user and group.i.e they are tied to the new ids not the old ones run this test on atleast more than one type of DB

    Description

      We should be able to backup course events when course backup is performed. And do that controlled by one setting in backup (defaulting to yes).

      See backup_events_info() under Moodle 1.9.

      Then, restore will allow to restore that information if available and also, optionally controlled by one setting.

      There is one open bug related to this since ages ago: MDL-13425 Perhaps we should fix that too, by adding one new setting on backup/restore to control if that piece of information is included. Or, at least, prevent events to be compied on import.

      Attachments

        Issue Links

          Activity

            People

              ankit_frenz Ankit Agarwal
              stronk7 Eloy Lafuente (stronk7)
              Aparup Banerjee Aparup Banerjee
              Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
              Rajesh Taneja Rajesh Taneja
              Adrian Greeve, David Woloszyn, Huong Nguyen, Jake Dallimore, Michael Hawkins, Stevani Andolo, David Woloszyn, Huong Nguyen, Jake Dallimore, Michael Hawkins, Stevani Andolo
              Votes:
              10 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                25/Jun/12