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

Beeping user in chat causes strict standard warning

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.4.6, 2.5.2
    • Fix Version/s: 2.4.7, 2.5.3
    • Component/s: Chat
    • Labels:
    • Testing Instructions:
      Hide
      1. Visit <yoursite>/admin/settings.php?section=modsettingchat and set 'Chat method' to 'Normal method'.
      2. Visit a course and create a chat activity.
      3. View this activity and click to enter the chat.
      4. Click on 'Beep' under your name.
      5. Check that there is no strict standard warning and the beep worked as expected.
      Show
      Visit <yoursite>/admin/settings.php?section=modsettingchat and set 'Chat method' to 'Normal method'. Visit a course and create a chat activity. View this activity and click to enter the chat. Click on 'Beep' under your name. Check that there is no strict standard warning and the beep worked as expected.
    • Affected Branches:
      MOODLE_24_STABLE, MOODLE_25_STABLE
    • Fixed Branches:
      MOODLE_24_STABLE, MOODLE_25_STABLE
    • Story Points:
      3
    • Sprint:
      BACKEND Sprint 6

      Description

      1. Visit <yoursite>/admin/settings.php?section=modsettingchat and set 'Chat method' to 'Normal method'.
      2. Visit a course and create a chat activity.
      3. View this activity and click to enter the chat.
      4. Click on 'Beep' under your name.
      5. You will see the message (obviously will vary depending on your site directory location) "Strict Standards: Creating default object from empty value in /var/www/mstorage/i24/moodle/mod/chat/gui_header_js/users.php on line 42"

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  11/Nov/13