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

"Local category field" option in database enrol plugin

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.3
    • 2.2.1
    • Enrolments
    • None
    • Any
    • MOODLE_22_STABLE
    • MOODLE_23_STABLE
    • w11_MDL-31845_m23_dbenrolcat
    • 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.

      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.)

            skodak Petr Skoda
            maherne Michael Aherne
            Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
            Ankit Agarwal Ankit Agarwal
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

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