Bug 21135 - Upon log in, user is redirected to account page instead of the page where they logged in from
Summary: Upon log in, user is redirected to account page instead of the page where the...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on: 31699
Blocks:
  Show dependency tree / graph
 
Reported: 2018-07-31 19:06 UTC by Caroline Cyr La Rose
Modified: 2023-03-28 13:11 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2018-07-31 19:06:49 UTC 
When a user clicks on a link "log in to ..." they are redirected to their account page instead of staying on the page they were on to do whatever they needed to log in to do.

To reproduce :

1- In Administration > System preferences, enable TagsEnabled
2- Make sure TagsInputOnDetail is set to Allow
3- Go to OPAC, and do a search
4- Click on title to go to the details page
5- Click on the "Log in to add tags" link
6- Enter your login credentials in the popup window

Result : user is redirected to "My account"
Desired result : user is now logged in but stays on the record detail page

Second case :

1- In OPAC, click on Lists > View All
2- Click on "Log in to create new lists"
3- Enter your login credentials

Result : user is redirected to "My account"
Desired result : user is now logged in but stays on the lists page
Comment 1 Liz Rea 2019-10-11 15:19:58 UTC 
I think this should happen any time a user clicks on a link that isn't explicitly "Log in to my account"

So any action that triggers a login because a user wants to do something (place a hold, create a list, send a cart, there are probably others) we should take them back to where they came from instead of to their account.
Comment 2 Katrin Fischer 2020-04-05 10:10:54 UTC 
(In reply to Liz Rea from comment #1)
> I think this should happen any time a user clicks on a link that isn't
> explicitly "Log in to my account"
> 
> So any action that triggers a login because a user wants to do something
> (place a hold, create a list, send a cart, there are probably others) we
> should take them back to where they came from instead of to their account.

+1
Comment 3 Lisette Scheer 2023-03-27 17:18:23 UTC 
(In reply to Liz Rea from comment #1)
> I think this should happen any time a user clicks on a link that isn't
> explicitly "Log in to my account"
> 
> So any action that triggers a login because a user wants to do something
> (place a hold, create a list, send a cart, there are probably others) we
> should take them back to where they came from instead of to their account.
+1
Comment 4 Martin Renvoize (ashimema) 2023-03-28 13:10:53 UTC 
See bug 31699 for the general approach we now have in code.. it can be used on any login links we wish.