This solved on my major headaches recently when I couldn’t get return or override return to work on a login form.
Many thanks!

Cog Design - 01 June 2010 08:01 AM

Hi Corey,

Managed to get my issue sorted, and it’s working great! However still experienced the same issue as Jim F (the ext. leaving out index.php) and had to modify the extension to include the index page.

Thanks,

Jack

How exactly did you modify the extension to include the index page?  My EE install is using “main” instead of “index.php”, and the extension is somehow losing the main/ section of my URLs.  Is there somewhere in the extension where I can just add main/ and have it included in the redirect page?

EDIT: I should mention… the redirect works perfectly on a logout, but it forgets the /main/ when logging in.

EDIT 2: Ok, looks like I was able to hack a solution.  For the time being, I’ve commented out the whole section of the extension that deals with the login process.  To handle the login redirect, I’m just using this:

@James Likeness, this way we still see the EE redirect login page though.

I wish the extension was updated.

deckard97 - 23 June 2010 09:45 PM

@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:

Yes, tried it.
Good as a workaround for now. Thanks.

Hello everyone, apologies for the slow response on the index.php issue.  We are working on a fix for this in the next couple of weeks, and will release updates for both 1.6/2.0.  I’ll post here when it’s up!

Ryan J. Bonnell - 13 May 2009 03:20 PM

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.