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

Comments report throws coding_exception for disabled modules

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 2.3.5
    • Comments, Reports
    • MOODLE_23_STABLE
    • Hide

      1. Create a wiki activity
      2. Add a comment to it
      3. Add a comment somewhere outside of a wiki activity.
      4. Go to Site administration / ►Reports / ►Comments and view the comments report. Your comments should be displayed.
      5. Go to Site administration / ►Plugins / ►Activity modules / ►Manage activities and hide the wiki module.
      6. Go back to the comments report and check that it still displays but that the wiki comment is not displayed.
      7. Unhide the wiki module.

      Show
      1. Create a wiki activity 2. Add a comment to it 3. Add a comment somewhere outside of a wiki activity. 4. Go to Site administration / ►Reports / ►Comments and view the comments report. Your comments should be displayed. 5. Go to Site administration / ►Plugins / ►Activity modules / ►Manage activities and hide the wiki module. 6. Go back to the comments report and check that it still displays but that the wiki comment is not displayed. 7. Unhide the wiki module.

      The comments report throws a coding exception if there exist an activity module that has comments, which has been disabled.

      Steps to reproduce:
      1. Create a wiki activity
      2. Add a comment to it
      3. Disable the wiki module
      4. View the comments report.

      I have also reproduced this with the database module.

            Unassigned Unassigned
            ashleyholman Ashley Holman (Inactive)
            Ankit Agarwal Ankit Agarwal
            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.