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

Coding error when adding/updating a chat with past/current time

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      1. Add a new Chat activity with Name and Description
      2. Set Next chat time to past or current time
      3. Set Repeat/Publish session times to No repeats - publish the specified time only
      4. Click Save and display

      Expected: Chat activity displayed
      Actual: Error message displayed (coding exception)

      Show
      1. Add a new Chat activity with Name and Description 2. Set Next chat time to past or current time 3. Set Repeat/Publish session times to No repeats - publish the specified time only 4. Click Save and display Expected: Chat activity displayed Actual: Error message displayed (coding exception)
    • Affected Branches:
      MOODLE_27_STABLE
    • Fixed Branches:
      MOODLE_27_STABLE
    • Pull from Repository:
    • Pull Master Branch:

      Description

      If you add/update a mod_chat activity to have the "Next chat time" as the default (current) time or in the past and set repeat/publish to "No repeats - publish the specified time only", on saving, you're presented with a coding exception from a calendar event:

      Exception: Coding error detected, it must be fixed by a programmer: The 'timestart' value must be set in other. in ./lib/classes/event/calendar_event_updated.php on line 110.
      Stack trace:
      line 110 of ./lib/classes/event/calendar_event_updated.php: coding_exception thrown
      line 252 of ./lib/classes/event/base.php: call to core\event\calendar_event_updated->validate_data()
      line 2365 of ./calendar/lib.php: call to core\event\base::create()
      line 653 of ./mod/chat/lib.php: call to calendar_event->update()
      line 37 of ./mod/chat/view.php: call to chat_update_chat_times()

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  10/Nov/14