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

"Local category field" option in database enrol plugin

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.3
    • Component/s: Enrolments
    • Labels:
      None
    • Database:
      Any
    • Testing Instructions:
      Hide

      To test patch:

      Configure database enrolment plugin to create sites from an external table with a category column.
      Create categories with idnumbers matching values in category column.
      Set "Local category field" setting to "idnumber".
      Run sync.

      New courses should be created in the correct categories.

      Show
      To test patch: Configure database enrolment plugin to create sites from an external table with a category column. Create categories with idnumbers matching values in category column. Set "Local category field" setting to "idnumber". Run sync. New courses should be created in the correct categories.
    • Affected Branches:
      MOODLE_22_STABLE
    • Fixed Branches:
      MOODLE_23_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      w11_MDL-31845_m23_dbenrolcat

      Description

      The current implementation of the database enrolment plugin requires the external database to know the internal Moodle row ID of the course category. Now that categories have an idnumber field it would make sense to have the option to match on idnumber instead, which would be consistent with the ability to select the matching local field for course, user and role.

      (This may be the same issue that is reported in MDL-28518, although that appears to be bound up with the ability to synchronise categories which is probably a separate feature.)

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  25/Jun/12