Is there anyway to get the login page to redirect back to the previous page? Is there something I can do to the skins Login link?

Hi
I have also tried that but when I login it goes to the current page that I was on.I am using 4.5.5 of dnn. If you are using some custom login controls then you may have set it to redirect to the home page after logging in

Hello,

By default DotNetNuke redirects to the previous page after login.

If you wish to redirect, there is also an option to specify a 'redirect to' page after login.

• go to admin menu / user accounts
• click on user settings
• in user accounts settings there is an option for redirect after login - select the page you require

I don't know if this will help, but you can always redirect to the same page, and have content on that page that depends on the user's security role.

I have always used the method that Joe mentions here. so when a user logs in, a piece of text is just displayed for that security role and the account login module is no longer displayed (view permissions set to unauthenticated users only).

- so when a user logs in they will have a line of text that states " you have successfully logged in click here to continue" - and that link directs them to the page you require.

It's not as automated as you require and I'm sure there is a way to set up a redirect, but the above method is how I have always implemented it.

If you'd like to seem some of these kinds of techniques in action, you can look at stockcentral.com. Register for the free trial and compare what some of the pages look like when logged in and when not logged in. I don't use a "you have successfully logged in" think because the logged in user's name is displayed in the upper right after login.

Yes that makes a lot of sense. I will try that.

Thanks very much.

Sorry to revisit this. I went to the User Settings and selected a particular page to be redirected to After Login. However, it's not happening. Any ideas? I restarted the Application and I even reset IIS. Nada.

Thanks, Mark.

I have a vague memory of reading somewhere that this feature is broking in current versions of DotNetNuke. And, I checked and there is an issue logged in the bug tracker. It's noted that a solution was checked in on 6/2, but it's not clear if this went into the 4.8.4 release.

Which version of DotNetNuke are you using?

 Hi Joe.  I'm using 4.5.1 but am contemplating the upgrade.  It's scary to contemplate.  I've been "poised" to upgrade for the last 2 months.  

Don't fear upgrading ... but do your homework first.

First, make backup copies of your website and database. Then, use those to create a testing site.

Try to upgrade your site to 4.6.2. Use the "upgrade" package to do it, and remember to carefully use the upgrade's release.config file to create a new web.config that contains all of your existing site's web.config modifications.

Once you've upgraded to 4.6.2 successfully, you can simply unzip the 4.8.4 upgrade onto the web directory and go through the upgrade again. You won't have to do the painful web.config modifications when you upgrade after 4.6.2. DotNetNuke now can take care of that for you. No pain, lots of gain!

Unless you've got some very special custom modules, you probably won't see problems. But if you do, you can fix them on your testing site.

When it comes time to upgrade your site, I'd recommend that you make new copies of your existing site, install that to your testing site, do the upgrade again, and then move the testing site to your live site. Be sure to keeps lots of copies of everything in the event that you need to revert to a previous step.

Once you've upgraded to 4.8.4, you probably won't be tempted to upgrade for at least a year. Version 4.8.4 is (presumably) the very last 4.x version and then next ones will be 5.x. You can probably wait for a few rounds of 5.x before contemplating another upgrade ...