Hello,

I am having a problem getting the Account Login module to redirect to the same page when it contains a querystring.

For example I am using indoogrid to pass a parameter to a page with the following url:

http://revitinfo.com/Revit_Forum/Attachments/ContentID/205.aspx

If the user is logged in, everything works great.  Everything works great period, but I was wanting to streamline the login a bit for users who haven't already logged in by locating a login module on the redirected page.

I am doing this because I am using the page in a smaller, consolidated window, that doesn't show all of the same Skin objects as my normal page.  So I had to add the actual Account login module to the page, because I didn't want the other login options.

Anyway, when I place the login module on the page, I am able to login, and it redirects, but to:

http://revitinfo.com/Revit_Forum/Attachments.aspx

It's getting rid of the Querystring.  All I am wanting the module to do is redirect to the exact same url as I am already on, querystring and all.

My DNN version is 05.02.01.

Any help is greatly appreciated.  I did find this one link that had something related to what I am saying, but, first it says it's already been fixed, and second, I tried copying the code they show in the bottom and replacing, and I get a site error...

Thanks in advance.

Hey thanks For the reply! Unfortunately, that's not the problem. I did about 4 hours of testing and research last night and read probably close to all if not all of the "simple" fixes. Based on the link that I provided at the bottom of my last post, it just seems that something in the core is still functioning improperly. The redirect works fine if I set the workflow up to take me to the login page. It puts a return URL parameter in the url and returns back all of my custom URL parameters.I have passed three before with this method. As I describe already, the prroblem occurs when the module exists on the same page I am trying to access. That page is visible to all, but has a module on it that needs the querystring "contentid" that gets passed to it by a click on the previous page. If a user who is not logged in clicks on the link, he goes to the same page as everyone else, just has to login using module on that page. At this point, the problem occurs because the module or core doesn't properly redirect to the same page, as in my example above,it leaves out the URL parameter "contentid" once the user logs in.

Any other thoughts or ideas would be greatly appreciated

I guess there are no other pros out there who have a thought about this? Does it sound like it could be a bug? If so, how should I report it?