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

User Tours Caveat - Courses and Dashboard

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.5
    • User Tours
    • None
    • MOODLE_405_STABLE

      Hi all,

      I've scanned the open issues and can't see anything related to this - if I've missed something, please do get this merged etc.
      As a little note, this issue was found in MWP but does also still appear to be apparent in Moodle itself, too.

      One of our clients are currently looking into creating User Tours on their site - they wanted to create one that launches when a user accesses '/my/courses.php' and also '/my/'.

      From Moodle documentation alongside trial and error, I can only get a tour to display on the Dashboard page '/my/' if the URL Match is set to ‘/my/%’ - note the '%' being used as a wildcard.
      This works perfectly and, once a user navigates to that page, the tour is shown.

      For the My Courses page, the URL Match needs to be '/my/courses.php'. Once again, this works perfectly.

      The problem comes about when both tours are used at the same time. The Dashboard tour ('/my/') will launch as soon as the user navigates to any page that has the path /my/ followed by something else because of the '%' wildcard - as the 'My Courses' page ends in /my/courses.php, the wrong tour is being shown to the user if they go to view their courses before their dashboard. 

      It feels like the Dashboard may need the same treatment as the Frontpage - you can add 'FRONTPAGE' instead of a URL/path to trigger the tour.

      Is this something that has been raised before?

      Thanks,
      Spencer

            Unassigned Unassigned
            spencer_cummins Spencer Cummins
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:

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