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

Implement core_privacy for core_calendar

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.3.5, 3.4.2, 3.5
    • Fix Version/s: 3.3.6, 3.4.3
    • Component/s: Calendar, Privacy
    • Labels:
    • Testing Instructions:
      Hide

      Testing steps:

      Moodle 3.5/3.4:

      1. Run PHP unit test calendar/tests/privacy_test.php
      2. Log in as Admin and create Calendar Events at Site, User, Category, Course context levels. (NOTE: Moodle 33 does not support Calendar Events / Subscriptions at the Category context level).
      3. As Admin create a Calendar Subscription at Site, User, Category, and Course context levels.
      4. As Admin create a Course and add a new Assignment with duedate, and gradingduedate values.
      5. Repeat creating Calendar Events and Subscriptions as a Teacher and Student.
      6. Run testwithmanager.php script to test core_calendar privacy compliance and data export (see -----------MDL-61571----------- for the original script location) in the Moodle root folder. Make sure you've purged the caches (php admin/cli/purge_caches.php), before running testwithmanager.php. You should receive a script output like:

        Testing the compliant plugins:
        .....
         
        == core_calendar (core_calendar\privacy\provider) ==
            Found 1 items of metadata
            Successfully ran a test export
        

      7. A single Calendar Event at a context level, time, and eventtype should be exported with JSON file path/name "Calendar/Events/{timestart}/{eventtype}-event.json",
      8. Multiple Calendar Events at the same context level, time, and eventtype should be exported with JSON file name/path "Calendar/Events/{timestart}/{eventtype}-event- {no}

        .json".

      9. A single Calendar Subscriptions at a context level, and eventtype should be exported with JSON file path/name "Calendar/Subscriptions/{eventtype}-subscription.json".
      10. Multiple Calendar Subscriptions at the same context level, and eventtype should be exported with JSON file name/path "Calendar/Subscriptions/{timestart}/{eventtype}-subscription-{no}.json".

      Moodle 3.3:

      • Repeat testing steps above without setting Calendar Events / Subscriptions at the Category context levels.
      Show
      Testing steps: Moodle 3.5/3.4: Run PHP unit test calendar/tests/privacy_test.php Log in as Admin and create Calendar Events at Site, User, Category, Course context levels. (NOTE: Moodle 33 does not support Calendar Events / Subscriptions at the Category context level). As Admin create a Calendar Subscription at Site, User, Category, and Course context levels. As Admin create a Course and add a new Assignment with duedate, and gradingduedate values. Repeat creating Calendar Events and Subscriptions as a Teacher and Student. Run testwithmanager.php script to test core_calendar privacy compliance and data export (see ----------- MDL-61571 ----------- for the original script location) in the Moodle root folder. Make sure you've purged the caches (php admin/cli/purge_caches.php), before running testwithmanager.php. You should receive a script output like: Testing the compliant plugins: .....   == core_calendar (core_calendar\privacy\provider) ==     Found 1 items of metadata     Successfully ran a test export A single Calendar Event at a context level, time, and eventtype should be exported with JSON file path/name "Calendar/Events/{timestart}/{eventtype}-event.json", Multiple Calendar Events at the same context level, time, and eventtype should be exported with JSON file name/path "Calendar/Events/{timestart}/{eventtype}-event- {no} .json". A single Calendar Subscriptions at a context level, and eventtype should be exported with JSON file path/name "Calendar/Subscriptions/{eventtype}-subscription.json". Multiple Calendar Subscriptions at the same context level, and eventtype should be exported with JSON file name/path "Calendar/Subscriptions/{timestart}/{eventtype}-subscription-{no}.json". Moodle 3.3: Repeat testing steps above without setting Calendar Events / Subscriptions at the Category context levels.
    • Affected Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_35_STABLE
    • Fixed Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE
    • Pull Master Branch:
      MDL-61693-master

      Description

      Implement privacy provider for core_calendar.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  17/May/18

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours
                  3h