@Ryan: Good to know, thanks for the confirmation and the kudos!
@boosh: sorry for the late reply. Are you still having trouble with this? We use the htaccess/no-index-php setup on all of our site, so it’s likely not a problem with that bit. Can you tell me a little more about your setup? (EE version, type of webserver, default template group, which template is set as home page?)
This extension collides with Ryan Irelan’s First Timer extension on my system, alas.
when I set the redirect page to last page visited it keeps trying to look for /login
I have my login in a pop up modal window and would like the redirect to be 2 pages ago and not last page visited, is there a way to get this with segments or something else?
This works but only returns to last page which is the modal window. I need to return to the page before this.
{exp:member:login_form return="{site_url}index.php/{segment_1}/{segment_2}/{segment_3}/{segment_4}"}@russlipton - Sorry about the conflict with First Timer. That looks like a good extension, and I’ve added a note to our queue (to take a look at that extension and see what it’ll take to sort out the conflicts).
@Eastwood Design - I’m not aware of a way to go back two pages using segments, but EE does store a collection of your last few pages in the $SESS->tracker collection. e.g.,
$SESS->tracker['2']…would be two pages back. You’d have to get pretty nuts and bolts with it; modify an existing extension or write your own, or get into some PHP in the templates.
We’ve added a feature for “last page after login”. Thanks to Kevin for doing the heavy lifting on that. You can download the updated version (1.1.0) from our site […]
Is version 1.1.0 of this extension available anywhere for download?
On the add-on page it lists version 1.0.0 as the current version (2007-12-23) and doesn’t seem to offer any new version for download. I’m wanting to take advantage of the “current page” setting mentioned earlier in the thread.
Is there a way using this extension to have it ignore specific login forms?
I’m developing a site where I’m using two different Login Forms to redirect users to a destination (Admins get redirected after login to /accounts, while Members get sent to another template group, /reports).
For example, with this extension enabled, it seems to overwrite the “return” parameter of all login forms, even when using the Login Form Tag with a custom return parameter set. When the extension is disabled, the return parameters are honored on all login forms.
What I’d love to see as a feature request is more granular control over what Login Forms get overwritten, instead of an all-or-nothing approach. Perhaps a setting could be developed to overlook/ignore login form on specific templates?
http://www.twomile.com/services/add-on/expression-engine-redirect-after-login
Ok, the add-on page has been updated… 1.1.0 is available there again. Sorry for that gaffe, and thanks very much for reporting it.
This extension does indeed hijack the return handling… it uses the central member login hook to do so, but we might be able to do some more intelligent filtering to figure out which form the user was on when they came in. Another approach might be to set different handling for different user groups.
Good suggestion, I’ll put that in the feature request list. We’re pretty buried in client work at the moment so we don’t have a schedule for the next release, but if anyone else wants to tackle this in the meantime we’ll happily merge a patch or two.
http://www.twomile.com/services/add-on/expression-engine-redirect-after-login This extension does indeed hijack the return handling… it uses the central member login hook to do so, but we might be able to do some more intelligent filtering to figure out which form the user was on when they came in. Another approach might be to set different handling for different user groups. Good suggestion, I’ll put that in the feature request list. We’re pretty buried in client work at the moment so we don’t have a schedule for the next release, but if anyone else wants to tackle this in the meantime we’ll happily merge a patch or two.
I’m looking forward to any updates regarding this addition. It’s a feature I could use even today. Thanks so much!
Hi @peternrg, we’re not actively developing this extension at the moment. Since it’s stable in its limited functions, we’re letting it sit while we tackle some client work and wait to see what EE2 brings. I’ve been expecting the new version would render our little extension obsolete, but I haven’t actually verified that. Anyone know how 2.0 is handling login redirection?
Hi @LHDesign, we use htaccess rewriting in all of our project sites, so that’s not a scenario we’ve tried. It might work if you just write it out that way in the config (/index.php?foo=bar) but I wouldn’t guarantee it. I’d be interested to hear from other folks that have tried that, or that have some experience with login redirection in EE2.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.