Verifying both name and password (was: New Problem)

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 13975
interpreted = N
texte = >In the invoice tmpl, if the customer does not enter one of the required parameters (number >or password) it just says: You must fill in the 'password' field on the form, so the >customer can fill anything in this field and it will work ok. If he'll enter WRONG number, >he'll get the WRONG address in the next page, that's all. If he fills the number right and >the password wrong, he'll get right address on the next page. >I want to avoid this situation and to poceed only if the number and the password are OK >and notify the client if the password does not fit the number. Is that possible?We do something like this in the MultiGroupChecker file. We check to see if the username is found, and if so then we check to see if the password matches that username. I would put those kinds of checks into the next page, and wrap the entire page inside a showif that only allows the rest of the page to appear if the number/password match.Open your MultiGroupChecker file to see how we did this.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== Pacific Coast Software | WebCatalog, WebMerchant 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: Verifying both name and password (was: New Problem) (natasha 1997)
  2. Re: Verifying both name and password (was: New Problem) (natasha 1997)
  3. Re: Verifying both name and password (was: New Problem) (Grant Hulbert 1997)
  4. Verifying both name and password (was: New Problem) (Grant Hulbert 1997)
>In the invoice tmpl, if the customer does not enter one of the required parameters (number >or password) it just says: You must fill in the 'password' field on the form, so the >customer can fill anything in this field and it will work ok. If he'll enter WRONG number, >he'll get the WRONG address in the next page, that's all. If he fills the number right and >the password wrong, he'll get right address on the next page. >I want to avoid this situation and to poceed only if the number and the password are OK >and notify the client if the password does not fit the number. Is that possible?We do something like this in the MultiGroupChecker file. We check to see if the username is found, and if so then we check to see if the password matches that username. I would put those kinds of checks into the next page, and wrap the entire page inside a showif that only allows the rest of the page to appear if the number/password match.Open your MultiGroupChecker file to see how we did this.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== Pacific Coast Software | WebCatalog, WebMerchant 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

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:

add line item context and showitems (1998) Funny Submissions From a Form Page (1999) Re[2]: New syntax feedback for 4.0 (2000) shipcost (1997) WebTen? (1997) The Guru Speaks-Is That Really the Only Manuel? (1998) TRAINING videos - Prove IT. (1998) 2.0 Info (1997) problems with 2 tags shakur (1997) Rhapsody? (1997) WebDNA 6.0 backwards compatible? (2004) Help! WebCat2 bug (1997) Newbie questions (2000) Web Logs (1998) New Guestbook Source (1997) Updating database (1998) [WebDNA] Brian Harrington (2019) Multiple prices (1997) Erotic Sites (1997) (1998)