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

Sections cache may cause some resources fail opening/refreshing

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.7.2
    • Fix Version/s: 3.8.0
    • Component/s: URL add-on
    • Labels:
    • Testing Instructions:
      Hide

      This issue only needs to be tested in 1 device.

      1. In the app, login as a student and open a certain section in a course.
      2. In web as teacher, create a new URL resource in that section and make it point to an external page (e.g. https://google.es). Make sure to configure Appearance > Display as "Automatic".
      3. In the app, perform a PTR in the section. Check that the new URL resource appears and it has the "link" button next to it.
      4. Click that "link" button. Check that the URL's page is opened in the browser (the URL you set in step 2, e.g. Google).
      5. Now open the URL. Check that you can view the URL link in the app (e.g. the Google URL).
      6. In web as teacher, edit the URL and make it point to a different site (e.g. moodle.org).
      7. In the app, perform a PTR in the URL's page. Check that the URL displayed changes to the new one.
      8. In web as teacher, create a new LTI activity. Set a certain "Icon URL" and "Secure icon URL" (same value in both fields). If you already have an LTI activity with an icon set you can skip this step.
      9. In the app, open the section that contains that LTI activity. Check that you can see the custom icon you set in the previous step.
      10. In web as teacher, edit the LTI and set a different icon.
      11. In the app, perform a PTR in the section. Check that the icon is updated.
      Show
      This issue only needs to be tested in 1 device. In the app, login as a student and open a certain section in a course. In web as teacher, create a new URL resource in that section and make it point to an external page (e.g. https://google.es).  Make sure to configure Appearance > Display as "Automatic". In the app, perform a PTR in the section. Check that the new URL resource appears and it has the "link" button next to it. Click that "link" button. Check that the URL's page is opened in the browser (the URL you set in step 2, e.g. Google). Now open the URL. Check that you can view the URL link in the app (e.g. the Google URL). In web as teacher, edit the URL and make it point to a different site (e.g. moodle.org). In the app, perform a PTR in the URL's page. Check that the URL displayed changes to the new one. In web as teacher, create a new LTI activity. Set a certain "Icon URL" and "Secure icon URL" (same value in both fields). If you already have an LTI activity with an icon set you can skip this step. In the app, open the section that contains that LTI activity. Check that you can see the custom icon you set in the previous step. In web as teacher, edit the LTI and set a different icon. In the app, perform a PTR in the section. Check that the icon is updated.
    • Affected Branches:
      MOODLE_37_STABLE
    • Fixed Branches:
      MOODLE_38_STABLE
    • Sprint:
      Moodle App 3.8.0

      Description

      Case 1

      1. From the app, enter into a course.
      2. From the website add URL activity into the course.
      3. PTR the course and try to open it.

      Case 2

      1. From the app, enter into a course and a URL resource.
      2. From the website change the URL of the URL activity.
      3. Enter again, PTR the index page of the URL. The url is not updated.

      module.contents on url module-handler action is empty. It will call loadModuleContents, then getModule and then getSections. The module won't be found on the returned sections.

      After clearing the cache, it works.

      It can happen with other resources but url is an easy test.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                20/Dec/19