I think there are two scenarios, based on my own use:
1. I (as the user) click on some action that requires login. I want to go straight to the function after authentication. The obvious link/function currently is "save to favorites," but it also seems like a site could legitimately want to display links
to the recall function before the user logs in, or to MyAccount information. In any those cases I as a user want the user to go directly to the function after authentication.
2. I want to log in without having a specific function function in mind. Maybe I'm searching and click "Login" in the upper right, so I can get the recall links and others that are only available when logged in. In that case, I want to return to the same
page after authentication.
Those are the behaviors that I have come to expect, and I think that is true of our users in general. So I think it would make sense for VF2 to move in that direction.
How it might happen or what the priority would be is another question entirely.
University of Chicago Library
Does the user always get redirected to favorites, or only if they click on the “login” link at the top of the page.
The CAS authentication module is not a standard part of VuFind, so I’m not sure how it impacts login behavior.
The standard behavior is that logging in through the “login” link at the top always sends the user to the default logged in module (which is usually Favorites unless configured otherwise in config.ini). If you perform
an action that requires a login, however (like adding a tag or storing a favorite), you shouldn’t get redirected away after logging in.
So if you need the login at the top of the page to redirect back, that’s a new VuFind feature that needs to be added. If you are having problems with getting redirected while in the middle of operations like tagging
or saving, that is probably a CAS-related bug.
Unfortunately, the code in VuFind 1.x that handles redirection is hideously convoluted – getting rid of it was one of my motivations for tackling the VuFind 2.0 project. If upgrading to 2.0 is on your agenda, it might
be best to deal with this issue as part of the upgrade process. On the other hand, if your instance of 1.3 is going to be in play for a long time, we can discuss this further and hopefully brainstorm a workaround. I have some ideas that I can share once
I know the exact extent of your problem.
(On the subject of 2.0, there is not yet a CAS implementation for the new version… but if you plan on upgrading, I would be happy to work with you on getting things working so we can have CAS support in the official
distributions rather than simply as a JIRA patch).
I was wondering if anyone has found a way to have it login to the page the user was currently on? As when I try logging in from different spots it always redirects me to the favorites page.
I am using CAS for authentication, Symphony 3.3.1 and Vufind 1.3
Thanks for any help or ideas!
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
VuFind-General mailing list