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

Miscellaneous category cannot be opened after courses are created by log in

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.4.1
    • Component/s: Course, Navigation
    • Labels:
    • Environment:
      SLES11 release 2
    • Database:
      PostgreSQL
    • Testing Instructions:
      Hide

      1/ install moodle
      2/ create more than 20 courses in Misc category (may be less if you lower $CFG->navcourselimit)
      3/ try to add new course - verify exception is not triggered any more

      Show
      1/ install moodle 2/ create more than 20 courses in Misc category (may be less if you lower $CFG->navcourselimit) 3/ try to add new course - verify exception is not triggered any more
    • Workaround:
      Hide

      Create a new category (besides Miscellaneous) and the problem will disappear.

      Show
      Create a new category (besides Miscellaneous) and the problem will disappear.
    • Affected Branches:
      MOODLE_24_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      w51_MDL-37105_m25_catlimit

      Description

      Error message: "Coding error detected, it must be fixed by a programmer: moodle_database::get_in_or_equal() does not accept empty arrays"

      This has happened with a setup identical to previous ldap setup, which worked on 2.2 and 2.3.
      It happens if I upgrade a 2.3.3 to 2.4 or if I make a fresh install.

      Courses are created at log in on our server, we have used this setup for years with no problems.
      Setup between ldap and moodle has not been changed on upgrade..

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  14/Jan/13