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

Any #hash deep links eg forum permalinks are lost during login process

XMLWordPrintable

    • MOODLE_29_STABLE, MOODLE_30_STABLE
    • MOODLE_29_STABLE, MOODLE_30_STABLE
    • MDL-53047-login-anchor
    • Hide

      Find any deep link which includes a #hash anchor such as found in the links that the forum sends out.

      1. Make sure you are not logged in.
      2. Go to the permalink url with the anchor.
      3. You'll get redirected to login page, login
      4. See that the anchor has been lost in the login process

      Apply the patch, repeat and you should retain the anchor and scroll down to the correct post

      Also repeat this process and at the login page type in a wrong password, and then on the second attempt login correctly.

      Show
      Find any deep link which includes a #hash anchor such as found in the links that the forum sends out. Make sure you are not logged in. Go to the permalink url with the anchor. You'll get redirected to login page, login See that the anchor has been lost in the login process Apply the patch, repeat and you should retain the anchor and scroll down to the correct post Also repeat this process and at the login page type in a wrong password, and then on the second attempt login correctly.

      ie you get an email to a forum, click on the deep link which includes the #p1234, get asked to login, and then after a redirect the hash is removed because the server never gets it.

      I found this while testing MDL-51196.

            brendanheywood Brendan Heywood
            brendanheywood Brendan Heywood
            David Monllaó David Monllaó
            Andrew Lyons Andrew Lyons
            Simey Lameze Simey Lameze
            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.