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

framework_autocomplete element causes DB error to be thrown

    XMLWordPrintable

    Details

    • Affected Branches:
      MOODLE_31_STABLE
    • Fixed Branches:
      MOODLE_31_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-56720-master
    • Pull Master Diff URL:
    • Testing Instructions:
      Hide
      1. Login as admin.
      2. Go to Site administration ► Competencies ► Migrate frameworks.
      3. Enter "a" in either "Migrate from" or "Migrate to" fields.
      4. Click "Cancel".
        • Confirm that a DB error does not occur.
        • Confirm that the page refreshes and the form is reset.
      5. Go to Site administration ► Competencies ► Competency frameworks
      6. Add a new competency framework CF1.
      7. Add a competency C1 under CF1.
      8. Add another new competency framework CF2
      9. Add a competnecy C1 under CF2.
      10. Go back to Site administration ► Competencies ► Migrate frameworks
      11. Enter "a" in either "Migrate from" or "Migrate to" fields.
      12. Click "Perform migration"
        • Confirm that a DB error does not occur.
        • Confirm that form validation errors are shown instead.
      13. Select CF1 for "Migrate from"
      14. Select CF2 for "Migrate to"
      15. Click "Perform migration"
        • Confirm that a DB error does not occur.
        • Confirm that the frameworks are migrated successfully.
      Show
      Login as admin. Go to Site administration ► Competencies ► Migrate frameworks . Enter "a" in either "Migrate from" or "Migrate to" fields. Click "Cancel". Confirm that a DB error does not occur. Confirm that the page refreshes and the form is reset. Go to Site administration ► Competencies ► Competency frameworks Add a new competency framework CF1. Add a competency C1 under CF1. Add another new competency framework CF2 Add a competnecy C1 under CF2. Go back to Site administration ► Competencies ► Migrate frameworks Enter "a" in either "Migrate from" or "Migrate to" fields. Click " Perform migration " Confirm that a DB error does not occur. Confirm that form validation errors are shown instead. Select CF1 for " Migrate from " Select CF2 for " Migrate to " Click " Perform migration " Confirm that a DB error does not occur. Confirm that the frameworks are migrated successfully.

      Description

      The framework_autocomplete element causes DB error to be thrown when a search value is entered for a framework that does not exist. To reproduce:

      1. Login as admin.
      2. Go to Site administration ► Competencies ► Migrate frameworks.
      3. Enter "a" in either "Migrate from" or "Migrate to" fields.
      4. Click "Cancel" or "Perform migration".
      5. Expected
        • There should be no DB error.
      6. Actual:
        • A DB error occurs

        Attachments

          Issue Links

          Discovered while testing

          Bug - A problem which impairs or prevents Moodle from functioning correctly. MDL-56481 Error cancelling migration of a framework

          • Minor - Minor loss of function where workaround is possible
          • Closed

            Activity

              People

              Assignee:
              jpataleta Jun Pataleta
              Reporter:
              jpataleta Jun Pataleta
              Peer reviewer:
              David Monllaó David Monllaó
              Integrator:
              Dan Poltawski Dan Poltawski
              Tester:
              Rajesh Taneja Rajesh Taneja
              Participants:
              Component watchers:
              Andrew Lyons, Dongsheng Cai, Huong Nguyen, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze, Jean-Philippe Gaudreau, Steve Massicotte, Serge Gauthier, Issam Taboubi, Adrian Greeve, Jake Dallimore, Mathew May, Mihail Geshoski, Peter Dias, Sujith Haridasan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Fix Release Date:
                14/Nov/16