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

Frontpage combo list double linking by filters



    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0.1
    • Component/s: Glossary
    • Labels:
    • Environment:
      Ubuntu 10.04 Moodle 2.0 Weekly
    • Database:
    • Affected Branches:
    • Fixed Branches:


      This is probably two tickets in one...

      I migrated our server from a RedHat Enterprise 5 server running Moodle 1.9.5+ to an Ubuntu 10.04 Server, then upgraded to Moodle 2.0+ Weekly. Our glossary was on the front page with 10 or so entried and auto-linking enabled. One of the entries was "IT" and we have 2 courses in our course listing on the front page where the "IT" in the course name was auto-linked to the glossary entry and the rest of the course name was not linked to anything. In order to actually get into the IT Support Course, you had to click on the main category Davis College Department Courses and then you can click on the IT Support course.

      We simply deleted the glossary to get around it.

      I then decided to re-add the glossary activity and tried to enter a single entry in concept I put IT and filled out the rest. When I saved it, I received
      Field "LOWER(concept)" does not exist in table "glossary_entries"

      I described the mdl_glossary_entries and here is what I have...
      mysql> describe mdl_glossary_entries;

      Field Type Null Key Default Extra


      id bigint(10) unsigned NO PRI NULL auto_increment
      glossaryid bigint(10) unsigned NO MUL 0  
      userid bigint(10) unsigned NO MUL 0  
      concept varchar(255) NO MUL    
      definition text NO   NULL  
      definitionformat tinyint(2) unsigned NO   0  
      definitiontrust tinyint(2) unsigned NO   0  
      attachment varchar(100) NO      
      timecreated bigint(10) unsigned NO   0  
      timemodified bigint(10) unsigned NO   0  
      teacherentry tinyint(2) unsigned NO   0  
      sourceglossaryid bigint(10) unsigned NO   0  
      usedynalink tinyint(2) unsigned NO   1  
      casesensitive tinyint(2) unsigned NO   0  
      fullmatch tinyint(2) unsigned NO   1  
      approved tinyint(2) unsigned NO   1  


      Is this an improper table? Should it actually reference table $prefix_glossary_entries?




            • Assignee:
              stronk7 Eloy Lafuente (stronk7)
              digitalmess Aaron Cowell
              Component watchers:
              Adrian Greeve, Jake Dallimore, Mathew May, Mihail Geshoski, Peter Dias
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created:
                Fix Release Date: