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

Using an existing course ID number throws ugly exception.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Deferred
    • Icon: Minor Minor
    • None
    • 2.4.5, 2.5
    • Course
    • MOODLE_24_STABLE, MOODLE_25_STABLE
    • Hide
      Test 1
      1. Create a course and make note of the ID number used.
      2. Create another course (note - create, do not update an existing course) and attempt to use this ID number.
      3. Ensure an error message is displayed above the ID number field in the form.
      Test 2
      1. Create a course.
      2. Create another course and use a separate ID number - make note of this.
      3. Edit the first course you created and attempt to use the ID number.
      4. Ensure an error message is displayed above the ID number field in the form.
      Show
      Test 1 Create a course and make note of the ID number used. Create another course (note - create, do not update an existing course) and attempt to use this ID number. Ensure an error message is displayed above the ID number field in the form. Test 2 Create a course. Create another course and use a separate ID number - make note of this. Edit the first course you created and attempt to use the ID number. Ensure an error message is displayed above the ID number field in the form.

      When I create a course and use an existing shortname I get a nicely formatted error message above the field reading "Short name is already used for another course (C101)". However, when I use an existing Course ID number I get taken to another page that throws a moodle_exception with "ID number is already used for another course (C101)".

            markn Mark Nelson
            markn Mark Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

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