Re: Try not to laugh
This WebDNA talk-list message is from 2007
It keeps the original formatting.
numero = 68899
interpreted = N
texte = I also agree that it's human error. I have username systems on several of my sites, and until I stripped out potential leading and following spaces, I got a lot of errors from members. I think in some browsers the space is already there; the user doesn't actually type it in him/herself. I did something else on another site where the scheme is for WebCat to assign usernames and passwords, and people were having trouble. On the error page, I capture the entered username and password (and date and time) to a DB, and would check it periodically to help understand the user's assumptions. I could see plainly who was missing it and why, and changed the text on the password box to clarify the format the username should be. This helped a lot. But if anyone actually emailed saying it 'didn't work' I could look up in the DB to see what they had actually entered and let them know. Also, cookies. If you use cookies to store the logged in status, then obviously the user has to allow cookies. One more. Are you on WebStar by any chance? 3 or 4 years ago when it was time to upgrade to OSX, I opted to leave WebStar because the OSX upgrade I was facing doesn't handle incorrect logins well. It does as another list member said, and forces you to quit the browser before you could try again. (By this time I knew this would be a huge issue). If I were you, I'd code in a user/pass capture like I did in my 2nd para to at least see what she's typing in. Then you could prove human error. Hope that helps. Terry > >"I would be looking at the user causing the problem not your code" > >That is my first instinct. My background is systems engineering, >andI am a pretty good problem solver, but one of the most >importantrules of problem solving is to check your assumptions, so... -- Terry Wilson | terry@terryfic.com | http://terryfic.com http://WhosComing.com - a simplified, affordable online reservation system http://TightJacket.com -- stylish protection for your laptop -------------------------------------------------------------------------- Attitude is the only difference between ordeal and adventure. ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I also agree that it's human error. I have username systems on several of my sites, and until I stripped out potential leading and following spaces, I got a lot of errors from members. I think in some browsers the space is already there; the user doesn't actually type it in him/herself. I did something else on another site where the scheme is for WebCat to assign usernames and passwords, and people were having trouble. On the error page, I capture the entered username and password (and date and time) to a DB, and would check it periodically to help understand the user's assumptions. I could see plainly who was missing it and why, and changed the text on the password box to clarify the format the username should be. This helped a lot. But if anyone actually emailed saying it 'didn't work' I could look up in the DB to see what they had actually entered and let them know. Also, cookies. If you use cookies to store the logged in status, then obviously the user has to allow cookies. One more. Are you on WebStar by any chance? 3 or 4 years ago when it was time to upgrade to OSX, I opted to leave WebStar because the OSX upgrade I was facing doesn't handle incorrect logins well. It does as another list member said, and forces you to quit the browser before you could try again. (By this time I knew this would be a huge issue). If I were you, I'd code in a user/pass capture like I did in my 2nd para to at least see what she's typing in. Then you could prove human error. Hope that helps. Terry > >"I would be looking at the user causing the problem not your code" > >That is my first instinct. My background is systems engineering, >andI am a pretty good problem solver, but one of the most >importantrules of problem solving is to check your assumptions, so... -- Terry Wilson | terry@terryfic.com | http://terryfic.com http://WhosComing.com - a simplified, affordable online reservation system http://TightJacket.com -- stylish protection for your laptop -------------------------------------------------------------------------- Attitude is the only difference between ordeal and adventure. ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Terry Wilson
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Extended [ConvertChars] (1997)
Triggers (2004)
FEA REQ: One .hdr, multiple .db's (2003)
How to set suffix mapping on IIS 5.1 ... (2004)
Mozilla Firefox problem (2004)
BW in a search (2007)
Problem displaying search result (1997)
Generating Searches on the fly? (1999)
RE: IIS4b2 and WebCatalog b19 (1997)
[searchString] (1997)
emailer on Windows Beta 18 (1997)
converted seed value? (1998)
order in the search? (2003)
Problems with ^ could be solved with [REPLACE CHARACTERS] (1997)
Intermitent problem using [referrer] (1997)
Three new problems, maybe a fourth (1997)
[WebDNA] [PROTECT] - Log Out (2011)
Can you specify encoding=multiline? (2000)
Random Image (1998)
Error.html (1997)