Well, the login module has the login control inside an UpdatePanel that does an ajax postback and redirects will not work in the context of an ajax postback, so it while I can sort of fix this it will not be a perfect fix.

I will add this code:

if ((WebConfigSettings.PageToRedirectToAfterSignIn.Length > 0)&&(WebConfigSettings.UseRedirectInSignInModule))
{
login1.SetRedirectUrl = true;
UpdatePanel1.ChildrenAsTriggers = false;
}

which basically says if you have a hard coded url confiugred for redirect it will make it not use an ajax postback but instead do a full postback so redirect is possible. In testing it works ok as far as redirecting except that since it is not doing an ajax page update you won't see an error message if the credentials entered are incorrect. Also its possible that some feature content could disappear from the page during the full postback because some features only populate on non postback requests. 

So really there is no ideal fix for this and if you are using a hard coded redirect page it is probably best to not use the sign in module and only use the real login page.

I generally recommend against forcing a specific page redirect after sign in, in most scenarios it is not the best idea. For example if a user must sign in to post in the forums or sign in to complete a web store purchase the normal behavior will redirect him back to where he was in the forums or the store and this hard coded redirect bypasses that and can result in bad user experience and lost sales.

So if you have a special case where it really does make sense to have a hard coded redirect then I'm afraid the sign in module is not going to work ideally in that case.

Best,

Joe