gymnasticsmedia
Nuke Pro
Posts:70
 |
| 18 Sep 2007 9:06 AM |
|
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?
|
|
GymnasticsMeida.com
The Ultimate Portal for the Ultimate Sport |
|
|
Bobbyjosephg
Nuke Pro
Posts:69
|
| 19 Sep 2007 1:42 AM |
|
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 |
|
|
|
|
leesykes
DNN Creative Staff
Nuke Master III
Posts:3352
|
|
rogerg1967
DNN Creative Magazine Subscriber
Nuke Pro
Posts:71
|
| 20 Sep 2007 1:18 PM |
|
I have a similar issue but I need to redirect to different pages depending on security role. ie a client role would redirect to page 1 and an admin role would redirect to page 2 on login. If it is not possible to select by security role can you select it by user?
Thanks for your help.
Roger |
|
|
|
|
jncraig
DNN Creative Staff
Nuke Master II
Posts:2357
|
| 20 Sep 2007 8:19 PM |
|
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.
|
|
Joe Craig
DNN Creative Support
Subscribe to the website |
|
|
leesykes
DNN Creative Staff
Nuke Master III
Posts:3352
|
| 21 Sep 2007 2:36 AM |
|
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.
|
|
Lee Sykes
Site Administrator
Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts
Twitter: www.twitter.com/leesykes
 |
|
|
jncraig
DNN Creative Staff
Nuke Master II
Posts:2357
|
| 21 Sep 2007 6:28 AM |
|
| 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. |
|
Joe Craig
DNN Creative Support
Subscribe to the website |
|
|
rogerg1967
DNN Creative Magazine Subscriber
Nuke Pro
Posts:71
|
| 21 Sep 2007 10:38 AM |
|
Yes that makes a lot of sense. I will try that.
Thanks very much. |
|
|
|
|
mgordon
DNN Creative Magazine Subscriber
Nuke Master
Posts:105
|
| 08 Jul 2008 1:26 PM |
|
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. |
|
Mark Gordon
Webmonkey |
|
|
jncraig
DNN Creative Staff
Nuke Master II
Posts:2357
|
| 08 Jul 2008 7:11 PM |
|
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? |
|
Joe Craig
DNN Creative Support
Subscribe to the website |
|
|
mgordon
DNN Creative Magazine Subscriber
Nuke Master
Posts:105
|
| 09 Jul 2008 10:59 AM |
|
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. 
|
|
Mark Gordon
Webmonkey |
|
|
jncraig
DNN Creative Staff
Nuke Master II
Posts:2357
|
| 09 Jul 2008 11:14 AM |
|
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 ... |
|
Joe Craig
DNN Creative Support
Subscribe to the website |
|
|