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

Implement core_privacy for enrol plugins (not lti and paypal)

    XMLWordPrintable

    Details

    • Type: New Feature
    • 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: Enrolments, Privacy
    • Labels:
    • Testing Instructions:
      Hide

      These changes are covered by the unit tests for the manager.

      Also, you can testing by running the attached testwithmanager.php script (see --------MDL-61571-------- for the original script location) in the Moodle root folder. Make sure you've purged the cache (php admin/cli/purge_caches.php), before running testwithmanager.php.

      You should receive a script output like:

      Testing the compliant plugins:
      ...
      == enrol_category (enrol_category\privacy\provider) ==
          Claims not to store any data with reason:
            'The Category enrolments plugin does not store any personal data.'
      == enrol_cohort (enrol_cohort\privacy\provider) ==
          Claims not to store any data with reason:
            'The Cohort sync enrolments plugin does not store any personal data.'
      == enrol_database (enrol_database\privacy\provider) ==
          Claims not to store any data with reason:
            'The External database enrolments plugin does not store any personal data.'
      == enrol_flatfile (enrol_flatfile\privacy\provider) ==
          Claims not to store any data with reason:
            'The Flat file (CSV) enrolments plugin does not store any personal data.'
      == enrol_guest (enrol_guest\privacy\provider) ==
          Claims not to store any data with reason:
            'The Guest access enrolments plugin does not store any personal data.'
      == enrol_imsenterprise (enrol_imsenterprise\privacy\provider) ==
          Claims not to store any data with reason:
            'The IMS Enterprise file enrolments plugin does not store any personal data.'
      == enrol_ldap (enrol_ldap\privacy\provider) ==
          Claims not to store any data with reason:
            'The LDAP enrolments plugin does not store any personal data.'
      == enrol_manual (enrol_manual\privacy\provider) ==
          Claims not to store any data with reason:
            'The Manual enrolments plugin does not store any personal data.'
      == enrol_meta (enrol_meta\privacy\provider) ==
          Claims not to store any data with reason:
            'The Course meta link enrolments plugin does not store any personal data.'
      == enrol_mnet (enrol_mnet\privacy\provider) ==
          Claims not to store any data with reason:
            'The MNet remote enrolments plugin does not store any personal data.'
      == enrol_self (enrol_self\privacy\provider) ==
          Claims not to store any data with reason:
            'The Self enrolments plugin does not store any personal data.'
      ...
      

      Show
      These changes are covered by the unit tests for the manager. Also, you can testing by running the attached testwithmanager.php script (see -------- MDL-61571 -------- for the original script location) in the Moodle root folder. Make sure you've purged the cache (php admin/cli/purge_caches.php), before running testwithmanager.php. You should receive a script output like: Testing the compliant plugins: ... == enrol_category (enrol_category\privacy\provider) ==     Claims not to store any data with reason:       'The Category enrolments plugin does not store any personal data.' == enrol_cohort (enrol_cohort\privacy\provider) ==     Claims not to store any data with reason:       'The Cohort sync enrolments plugin does not store any personal data.' == enrol_database (enrol_database\privacy\provider) ==     Claims not to store any data with reason:       'The External database enrolments plugin does not store any personal data.' == enrol_flatfile (enrol_flatfile\privacy\provider) ==     Claims not to store any data with reason:       'The Flat file (CSV) enrolments plugin does not store any personal data.' == enrol_guest (enrol_guest\privacy\provider) ==     Claims not to store any data with reason:       'The Guest access enrolments plugin does not store any personal data.' == enrol_imsenterprise (enrol_imsenterprise\privacy\provider) ==     Claims not to store any data with reason:       'The IMS Enterprise file enrolments plugin does not store any personal data.' == enrol_ldap (enrol_ldap\privacy\provider) ==     Claims not to store any data with reason:       'The LDAP enrolments plugin does not store any personal data.' == enrol_manual (enrol_manual\privacy\provider) ==     Claims not to store any data with reason:       'The Manual enrolments plugin does not store any personal data.' == enrol_meta (enrol_meta\privacy\provider) ==     Claims not to store any data with reason:       'The Course meta link enrolments plugin does not store any personal data.' == enrol_mnet (enrol_mnet\privacy\provider) ==     Claims not to store any data with reason:       'The MNet remote enrolments plugin does not store any personal data.' == enrol_self (enrol_self\privacy\provider) ==     Claims not to store any data with reason:       'The Self enrolments plugin does not store any personal data.' ...
    • Affected Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_35_STABLE
    • Fixed Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE
    • Pull 3.4 Branch:
    • Pull Master Branch:
      MDL-61915-master

      Description

      Probably all null providers. (Not enrol_lti and enrol_paypal).

      enrol_category
      enrol_cohort
      enrol_database
      enrol_flatfile
      enrol_guest
      enrol_imsenterprise
      enrol_ldap
      enrol_manual
      enrol_meta
      enrol_mnet
      enrol_self

        Attachments

        1. results_33.txt
          48 kB
        2. results_34.txt
          48 kB
        3. results_master.txt
          48 kB

          Activity

            People

            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

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