Chad Heinle
skipping stones
Posts:14
 |
| 02-16-2009 12:41 PM |
|
Is it possible to redirect to a different page if a user enters the wrong information and trips the error information?
I'm using a single line login on the home page as well as a separate dedicated login page, but if an error trips on the home page, it pushes the other information down and messes up the formatting, so I'd rather that it go to the dedicated login page instead. |
|
|
|
|
Chad Nash
Posts:5260
|
| 02-17-2009 03:58 PM |
|
Hi. This is not currently a feature the module offers, you should be able to format that message within the login template (maybe set the width to a maximum of 100 or something? If needed setup a test page on Beta Springs where the login module is in a small column and we will make sure we can get it up and running so that the message does not mess up the page layout.
-Chad
|
|
|
|
|
Chad Heinle
skipping stones
Posts:14
|
| 02-24-2009 09:18 AM |
|
Hi Chad, thanks for the response.
I suppose I don't quite know what I need to have in there as the token to capture the login error. The Login Failed, remember that Passwords are case sensitive message pops up above the box currently (with the red triangle) and the result is that it pushes down the rest of the form.
I thought the [DNN_MESSAGE_LABEL] token was supposed to handle that but it would seem I was incorrect. Is there something I can control that handles this? |
|
|
|
|
Chad Heinle
skipping stones
Posts:14
|
| 03-26-2009 05:07 AM |
|
Hi Chad,
I'm trying to revisit this issue - how do I go about adding a page on Beta Springs? |
|
|
|
|
David To
river guide
Posts:2719
|
| 03-26-2009 06:19 AM |
|
At www.betasprings.com (username: host, password: dnnhost) and you have access of the control panel to add page. Be sure to add the page to the correct home page (ie. if you using Dynamic Forms, add it under the Dynamic Forms parent page). -- David |
|
|
|
|
Chad Heinle
skipping stones
Posts:14
|
| 03-26-2009 06:32 AM |
|
Ok, I've set up a page on Beta Springs (Dynamic Login > Fromatting Issue). Now if you enter in a username/password that doesn't exist, you'll get the error message that appears above the login (red exclamation icon with the text: Login Failed, remember that Passwords are case sensitive).
This is what I'm trying to get around - the height of the login box is about the height I have to work with, so if the error message appears, it pushes down the login box and messes up the page layout. Please let me know if there is any solution to this issue. |
|
|
|
|
Francisco Pérez Andrés
going with the flow
Posts:53
|
| 10-13-2009 11:19 PM |
|
I'm having the same problem. Is there a way of setting the location & appeareance for the login system messages? By the way, where can I find information about the tokens [DNN_MESSAGE_LABEL] and [DNN_LOGIN_LABEL]
Thanks,
Francisco
|
|
| Expertos DotNetNuke en Madrid - Blog DotNetNuke España |
|
|
tango
new to the springs
Posts:1
|
| 03-28-2010 12:51 AM |
|
Hi,
why you not solve this problem?
The [DNN_MESSAGE_LABEL] NOT WORK! so the message is always before the fields :-(
Please, solve this issue.
Regards
Roland
|
|
|
|
|
David To
river guide
Posts:2719
|
| 03-29-2010 08:53 AM |
|
HI, you can edit the login password message error under Admin / Languages. Choose "Local Resources", traverse to Dynamic Login / App_LocalResources and click on the "DynamicLogin.ascx" file and on the right side, you should see a bunch of fields. Find the resource "loginfailed.txt", it should say "Login Failed, remember that Passwords are case sensitive". -- David |
|
|
|
|
Francisco Pérez Andrés
going with the flow
Posts:53
|
| 03-30-2010 07:04 AM |
|
Hi David,
Our problem is not with the text of the message, but with where the message appears! Is it possible to change the place of the error messages, using the template?
Thanks,
Francisco |
|
| Expertos DotNetNuke en Madrid - Blog DotNetNuke España |
|
|
David To
river guide
Posts:2719
|
| 03-30-2010 01:29 PM |
|
HI, currently there is no way to change the location of the "Login Failed, remember that Passwords are case sensitive" due to the fact that it's using the default DNN message alert and that is where it goes. We will need to examine this and modify in the code to make it be placeable somewhere else. This would most likely be an enhancement going forward when time permits. -- David |
|
|
|
|