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

WS exception when pressing back to a page containing a user tour

XMLWordPrintable

    • MOODLE_38_STABLE
    • MOODLE_38_STABLE
    • Hide
      1. Login as admin
      2. Create a new user
      3. Log out
      4. Login as new user
      5. The Your Dashboard tour should start
      6. Press End tour
      7. Press on Private files
      8. Press the Back button on your browser
      9. Ensure you don't see a WS exception about missing tourconfig response
      Show
      Login as admin Create a new user Log out Login as new user The Your Dashboard tour should start Press End tour Press on Private files Press the Back button on your browser Ensure you don't see a WS exception about missing tourconfig response

      When logging in as a new user, the usertours plugin appears to generate an exception under some circumstances

      Error in response - Missing following required key in a single structure: tourconfig
      Error code: invalidresponse
      * line 436 of /lib/externallib.php: invalid_response_exception thrown
      * line 261 of /lib/externallib.php: call to external_api::clean_returnvalue()
      * line 81 of /lib/ajax/service.php: call to external_api::call_external_function()
      

            pholden Paul Holden
            pholden Paul Holden
            Marina Glancy Marina Glancy
            Sara Arjona (@sarjona) Sara Arjona (@sarjona)
            Janelle Barcega Janelle Barcega
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 30 minutes
                1h 30m

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