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

Course reset for Bigbluebutton does not delete logs

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 4.0
    • 4.0
    • BigBlueButton
    • MOODLE_400_STABLE
    • MOODLE_400_STABLE
    • Hide

      Note as there is no way to see what is in the Bigbluebutton table log, you will need access to the database.

      In a course:

      1. Create two bigbluebutton activitities B1 and B2 in the course C1
      2. Join both meeting
      3. Go to the course Admin menu  : More/Course reuse and select reset course
      4. Check Delete custom logs in the Bigbluebutton section
      5. Reset course
      6. Check that in the table the records from the course matching the course C1 have disappeared:

      SELECT COUNT(*)  bigbluebuttonbn_logs WHERE courseid=<C1ID>

      Show
      Note as there is no way to see what is in the Bigbluebutton table log, you will need access to the database. In a course: Create two bigbluebutton activitities B1 and B2 in the course C1 Join both meeting Go to the course Admin menu  : More/Course reuse and select reset course Check Delete custom logs in the Bigbluebutton section Reset course Check that in the table the records from the course matching the course C1 have disappeared: SELECT COUNT(*)  bigbluebuttonbn_logs WHERE courseid=<C1ID>

    Description

      When we use the course reset there is a checkbox to clear out all Bigbluebutton logs.

      However, even if checked, the logs are not cleared.

       

      Attachments

        Activity

          People

            lmdavid Laurent DAVID
            lmdavid Laurent DAVID
            Shamiso Jaravaza Shamiso Jaravaza
            Shamim Rezaie Shamim Rezaie
            Angelia Dela Cruz Angelia Dela Cruz
            Jesus Federico, Laurent DAVID
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              19/Apr/22

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours
                2h