Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-1136

Error message on failed request is ambiguous

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • 2.1
    • 2.1
    • Web Services
    • Hide
      1. Try to add a new site, enter an invalid URL and check that you still see the error message talking about Moodle 2.4.
      2. Once inside a site, go to a non-cached page and force a WS fail (e.g. if you're testing with a local Moodle you can stop apache or disconnect the device from the local network). Check that a new error message is shown.
      Show
      Try to add a new site, enter an invalid URL and check that you still see the error message talking about Moodle 2.4. Once inside a site, go to a non-cached page and force a WS fail (e.g. if you're testing with a local Moodle you can stop apache or disconnect the device from the local network). Check that a new error message is shown.
    • MOODLE_21_STABLE
    • MOODLE_21_STABLE

    Description

      While browsing moodle.org using the app I was trying to get to my calendar events and the request failed (it took a long time), the error message reported was:

      Cannot connect: Verify that your (sic) have typed correctly the URL and that your site uses Moodle 2.4 or later

      That message should be changed because as a user I am already connected to the site, and it worked so it is irrelevant to me.

      Note the typo in the message

      Attachments

        Activity

          People

            dpalou Dani Palou
            fred Frédéric Massart
            Frédéric Massart Frédéric Massart
            Juan Leyva Juan Leyva
            Juan Leyva Juan Leyva
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Clockify

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