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

Warnings in glossary module

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.5.5, 2.6.2
    • 2.5.4, 2.6.1
    • Glossary
    • MOODLE_25_STABLE, MOODLE_26_STABLE
    • MOODLE_25_STABLE, MOODLE_26_STABLE
    • wip-MDL-44287-master
    • Hide
      1. Create glossary with some entries
      2. Export entries
      3. Import entries in a new module, make sure there are no warnings
      4. Try to add/edit/delete categories in glossary, make sure there are no warnings

      Run behat test from MDL-44337

      Show
      Create glossary with some entries Export entries Import entries in a new module, make sure there are no warnings Try to add/edit/delete categories in glossary, make sure there are no warnings Run behat test from MDL-44337
    • BACKEND Sprint 11

      While converting logs in MDL-40059 I found some warnings in glossary module:

      1. When importing glossary entries into new glossary:

      Notice: Undefined property: stdClass::$assessed in /home/marina/repositories/master/moodle/mod/glossary/lib.php on line 816
       
      Warning: Creating default object from empty value in /home/marina/repositories/master/moodle/mod/glossary/import.php on line 144
      

      2. When editing/deleting categories there are warnings such as "You should not output before redirecting"

      Fixing those in a separate issue, since it's not related to logging and also may be backported. Also I'm adding a behat test for glossary categories

            marina Marina Glancy
            marina Marina Glancy
            Petr Skoda Petr Skoda
            Dan Poltawski Dan Poltawski
            Dan Poltawski Dan Poltawski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

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