@James Likeness, this way we still see the EE redirect login page though. I wish the extension was updated.
Correct, but if you use this for your login form code, you can return to your current page:
{exp:member:login_form return="{segment_1}/{segment_2}/{segment_3}/{segment_4}"}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?
I’m having the same problem. I have an “admin” login and a “member” login and I can’t separate the “login return” so it makes it impossible for admins to log in.
I would love to see this feature added somehow. I think member groups would work great for this.
Is this extension still being developed/supported?
I have a site, updated to EE 2.6.1 that’s running on an MSII server.
The login functionality worked fine in previous versions of EE, now the server displays a “http 405 verb not allowed” error message when the viewer submits the form.
The login works normally when the extension is deactivated.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.