Re: Try not to laugh

This WebDNA talk-list message is from

2007

It keeps the original formatting. numero = 68898
interpreted = N
texte = I agree, sometimes the only way to solve these problems is to sit and watch the user, I have solved so many problems this way. Funny how you can spend months making a system idiot proof only to be broken in the first hour by a user that has their own way of looking at things.Have the user tested for Dyslexia ... LOLOn 27 Apr 2007, at 9:13 AM, Stephen Reiss wrote:> "I would be looking at the user causing the problem not your code">> That is my first instinct. My background is systems engineering, > and I am a pretty good problem solver, but one of the most > important rules of problem solving is to check your assumptions, so...>> I put this out there hoping to find not even a solution to the > problem as such, but a mechanism that would allow the problem to be > something other than human error.>> The code works - I can not duplicate the problem, and it is > inconsistent. The usual nightmare.>> But, once I bill enough hours trying to solve it, then everyone > will believe me it is human error.>>>> Problem #1. Clients just LOVE putting in spaces where they >> shouldn't, I have a client responsible for assigning new users and >> for some reason they always put a space AFTER the username - >> therefore the new user could never login until the space had been >> removed from the record - GREP fixed that one.>> The opposite can also happen for users, they type in their >> username/password and a blank, therefore their username/password >> is incorrect. From the irregularity of the problem, I would be >> looking at the user causing the problem not your code if it has >> been working for a long time.>>>>>> On 27 Apr 2007, at 3:06 AM, Stephen Reiss wrote:>>>>> I am looking into the browser/platform question - since I am >>> removed from the person having trouble, it takes a while to >>> filter down.>>>>>> Here is the code (it works, has for years - in case I missed a >>> showif/hideif or something - this is a snippet from a hugely long >>> page). Notice that it is a loop - the original page is served if >>> there is an error, or if they pass through the check. Since the >>> client was getting the error page, the problem is in the sending >>> and or looking up of the pw pair.>>>>>> The User Name and Passwords each have their own check and >>> response routines. It was the user name that was failing >>> according to the error message she noted.>>>>>>>>> [hideif [1through]=yes]>>> [text show=f]cid=[idnum][/text]>>> >>> [/hideif]>>>>>>>>>>>>>>> [showif [uid1]!]>>> [hideif [uid1]^uid1]>>> [search db=database.db&eqUIDdata=[uid1]]>>>>>> [text show=f]uidf=[numfound][/text]>>> [/search]>>>>>> [showif [uidf]=0]>>> We are sorry, that username is not in our records.

>>>>>>>>>>>> >>> [/showif]>>>>>> [showif [uidf]=1]>>>>>> [search db=database.db&eqPWdata=[pw1]]>>> [text show=f]pwf=[numfound][/text][/search]>>>>>> [showif [pwf]=0]>>> We are sorry, that password is incorrect.

>>> If you need to, you can contact us for help:
>>>>>>>>> >>> [/showif][/showif]>>>>>> [showif [pwf]=1]>>>>>> [search db=database.db&eqPWdata=[pw1]]>>> [founditems]>>> [text show=f]vnum=[idnum][/text]>>> [text show=f]vname=[name][/text]>>> [/founditems]>>> [/search]>>> [text show=f]pwcheck=yes[/text]>>> [/showif]>>>>>>>>> [/hideif][/showif]>>>>>>>>>>>>>>> [showif [pwcheck]=yes]>>>>>>>>> [showif [twicethrough]!yes]>>>

>>> You are in
>>>>>>

>>>>>> [/showif]>>>>>>> Stephen Reiss wrote:>>>> [snip]>>>>>>>>>> Can you think of any reason the pw check would fail on occasion?>>>> [snip]>>>>>>>> Stephen,>>>>>>>> Can you post your code? Also note what browser she is using.>>>>>>>> Donovan>>>>>>>>>>>>>>>>>>>> -->>>> =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o>>>> DONOVAN D. BROOKE EUCA Design Center>>>> <- Web Development (specializing in eCommerce),->>>>> <- Desktop Publishing, Print Consulting, Labels ->>>>> <-Glass Products, off-hand Classes/studio rental->>>>>>>>> PH:> (608) 835-2476 | Forum:> http://egg.bz/forum/>>>> Web Sites:> http://www.euca.us & http://www.egg.bz>>>> =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o>>>>>>>> ------------------------------------------------------------->>>> 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 >>> digest@talk.smithmicro.com>>>>> Web Archive of this list is at: http://webdna.smithmicro.com/>>>>>>>>> ------------------------------------------------------------->>> 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 >> digest@talk.smithmicro.com>>>> Web Archive of this list is at: http://webdna.smithmicro.com/>>>>>> ------------------------------------------------------------->> 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 > digest@talk.smithmicro.com>>> Web Archive of this list is at: http://webdna.smithmicro.com/>>> -------------------------------------------------------------> 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 digest@talk.smithmicro.com>> Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------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:

Re: Try not to laugh ( Terry Wilson 2007)
Re: Try not to laugh ( Stuart Tremain 2007)
Re: Try not to laugh ( Stephen Reiss 2007)
Re: Try not to laugh ( Stuart Tremain 2007)
Re: Try not to laugh ( Stephen Reiss 2007)
Re: Try not to laugh ( Stephen Reiss 2007)
Re: Try not to laugh ( Bob Minor 2007)
Re: Try not to laugh ( Donovan Brooke 2007)
Re: Try not to laugh ( Matthew A Perosi 2007)
Try not to laugh ( Stephen Reiss 2007)

I agree, sometimes the only way to solve these problems is to sit and watch the user, I have solved so many problems this way. Funny how you can spend months making a system idiot proof only to be broken in the first hour by a user that has their own way of looking at things.Have the user tested for Dyslexia ... LOLOn 27 Apr 2007, at 9:13 AM, Stephen Reiss wrote:> "I would be looking at the user causing the problem not your code">> That is my first instinct. My background is systems engineering, > and I am a pretty good problem solver, but one of the most > important rules of problem solving is to check your assumptions, so...>> I put this out there hoping to find not even a solution to the > problem as such, but a mechanism that would allow the problem to be > something other than human error.>> The code works - I can not duplicate the problem, and it is > inconsistent. The usual nightmare.>> But, once I bill enough hours trying to solve it, then everyone > will believe me it is human error.>>>> Problem #1. Clients just LOVE putting in spaces where they >> shouldn't, I have a client responsible for assigning new users and >> for some reason they always put a space AFTER the username - >> therefore the new user could never login until the space had been >> removed from the record - GREP fixed that one.>> The opposite can also happen for users, they type in their >> username/password and a blank, therefore their username/password >> is incorrect. From the irregularity of the problem, I would be >> looking at the user causing the problem not your code if it has >> been working for a long time.>>>>>> On 27 Apr 2007, at 3:06 AM, Stephen Reiss wrote:>>>>> I am looking into the browser/platform question - since I am >>> removed from the person having trouble, it takes a while to >>> filter down.>>>>>> Here is the code (it works, has for years - in case I missed a >>> showif/hideif or something - this is a snippet from a hugely long >>> page). Notice that it is a loop - the original page is served if >>> there is an error, or if they pass through the check. Since the >>> client was getting the error page, the problem is in the sending >>> and or looking up of the pw pair.>>>>>> The User Name and Passwords each have their own check and >>> response routines. It was the user name that was failing >>> according to the error message she noted.>>>>>>>>> [hideif [1through]=yes]>>> [text show=f]cid=[idnum][/text]>>> >>> [/hideif]>>>>>>>>>>>>>>> [showif [uid1]!]>>> [hideif [uid1]^uid1]>>> [search db=database.db&eqUIDdata=[uid1]]>>>>>> [text show=f]uidf=[numfound][/text]>>> [/search]>>>>>> [showif [uidf]=0]>>> We are sorry, that username is not in our records.

>>>>>>>>>>>> >>> [/showif]>>>>>> [showif [uidf]=1]>>>>>> [search db=database.db&eqPWdata=[pw1]]>>> [text show=f]pwf=[numfound][/text][/search]>>>>>> [showif [pwf]=0]>>> We are sorry, that password is incorrect.

>>> If you need to, you can contact us for help:
>>>>>>>>> >>> [/showif][/showif]>>>>>> [showif [pwf]=1]>>>>>> [search db=database.db&eqPWdata=[pw1]]>>> [founditems]>>> [text show=f]vnum=[idnum][/text]>>> [text show=f]vname=[name][/text]>>> [/founditems]>>> [/search]>>> [text show=f]pwcheck=yes[/text]>>> [/showif]>>>>>>>>> [/hideif][/showif]>>>>>>>>>>>>>>> [showif [pwcheck]=yes]>>>>>>>>> [showif [twicethrough]!yes]>>>

>>> You are in
>>>>>>

DOWNLOAD WEBDNA NOW!

Re: Try not to laugh

2007

Top Articles:

Related Readings:

User Name:
Password:

User Name:
Password:

User Name:
Password:

User Name:
Password: