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

Error in My Courses: mypage param is no accessible on core_block_get_dashboard_blocks

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 4.0.2
    • 4.0.1
    • My courses
    • Hide

      This issue only needs to be tested in 1 device.

      1. Login in a 3.X site with dashboard & site home disabled. See private comment.
      2. Check that the app displays the My Courses tab. Check that the list of courses is correctly displayed, and you don't see an error saying "mypage param is no accessible...".
      Show
      This issue only needs to be tested in 1 device. Login in a 3.X site with dashboard & site home disabled. See private comment. Check that the app displays the My Courses tab. Check that the list of courses is correctly displayed, and you don't see an error saying "mypage param is no accessible...".
    • MOODLE_400_STABLE
    • MOODLE_400_STABLE
    • Moodle App 4.0.2

      This happens when Dashboard and Site Home are disabled in a 3.X site, in that case we display the My Courses page. However, when trying to fetch the blocks for the My Courses page the app assumes the site needs to be 4.0, but it isn't in this case so the app displays an error.

      We shouldn't display this error in this case, and IMO we shouldn't display the side blocks because there are no blocks specific for My Courses (the blocks are for Dashboard, and it's disabled).

        1. Screenshot 2022-06-28 at 11.27.41.png
          Screenshot 2022-06-28 at 11.27.41.png
          748 kB

            dpalou Dani Palou
            dpalou Dani Palou
            Pau Ferrer Pau Ferrer
            Isabel Renedo Rouco Isabel Renedo Rouco
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

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