Re: REALLY need a hand

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 23841
interpreted = N
texte = At 5:38 AM 2/18/99, Nitai wrote: >1. If there are spaces in the adress fields or in the phone number then in >the form field it looks like this: >adress: Street to live Looks like: street >phone: 619-67865-1 Looks like: 619You need to put quotes around the value in each of your inputs, like this: ^ ^ Most browsers will interpret the next space (or hyphen, apparently as the end of the value. In fact, quotes are required by the HTML spec in all attribute/value pairs.For saftey's sake you should also wrap your values in [input], like this: ^^^^^^^ ^^^^^^^^ This will avoid potential problems with users inputting things like quotes and ampersands.>2. If the customers leave one field emtpy while registering, the emtpy field >is filled with or [adress2] after getting the customers address >back into the form.The changes outlined above should fix this as well.>3. If two customers have the same password, the form is filled with the >customer who comes first in the profile.db. Of course this is bad. But I >think it is only a wrong search string. Any help? >[search db=profile.db&eqpassworddatarq=[password]&eqemailrq=[email]&max=1]I think your password problem stems from a problem in your search sytax. eqemailrq=[email] is incorrect, so no searching is being done on the email field. Only the password field is being searched, so you are coming up with the wrong records. The correct syntax is eqemaildatarq=[email] You will probably want to add emailBlnk=T and passwordBlnk=T to your search criteria as well. Otherwise a user has to enter only the password or only email address, but not both, in order to view a record. So I'd try this search string: [search db=profile.db&eqpassworddatarq=[password]&passwordBlnk=T&eqemaildatarq=[email]&e mailBlnk=T&max=1]Also, unless you are using the [password] value entered into the browser's security dialog, it would be a good idea to change your field name to [pass] or [pword] or something else. Otherwise, you will run into conflicts with the built-in variable [password] when you try to use browser authentication somewhere down the line.Hope this helps.-Dave o--------------- Dave MacLeay --+ o----------- Digital Frontier --+ o--------------- 802.253.8612 --+ o--- dave@digitalfrontier.com --+ Associated Messages, from the most recent to the oldest:

    
  1. Re: REALLY need a hand (Dave MacLeay 1999)
  2. REALLY need a hand (Nitai 1999)
At 5:38 AM 2/18/99, Nitai wrote: >1. If there are spaces in the adress fields or in the phone number then in >the form field it looks like this: >adress: Street to live Looks like: street >phone: 619-67865-1 Looks like: 619You need to put quotes around the value in each of your inputs, like this: ^ ^ Most browsers will interpret the next space (or hyphen, apparently as the end of the value. In fact, quotes are required by the HTML spec in all attribute/value pairs.For saftey's sake you should also wrap your values in [input], like this: [input][name][/input] SIZE=30> ^^^^^^^ ^^^^^^^^ This will avoid potential problems with users inputting things like quotes and ampersands.>2. If the customers leave one field emtpy while registering, the emtpy field >is filled with or [adress2] after getting the customers address >back into the form.The changes outlined above should fix this as well.>3. If two customers have the same password, the form is filled with the >customer who comes first in the profile.db. Of course this is bad. But I >think it is only a wrong search string. Any help? >[search db=profile.db&eqpassworddatarq=[password]&eqemailrq=[email]&max=1]I think your password problem stems from a problem in your search sytax. eqemailrq=[email] is incorrect, so no searching is being done on the email field. Only the password field is being searched, so you are coming up with the wrong records. The correct syntax is eqemaildatarq=[email] You will probably want to add emailBlnk=T and passwordBlnk=T to your search criteria as well. Otherwise a user has to enter only the password or only email address, but not both, in order to view a record. So I'd try this search string: [search db=profile.db&eqpassworddatarq=[password]&passwordBlnk=T&eqemaildatarq=[email]&e mailBlnk=T&max=1]Also, unless you are using the [password] value entered into the browser's security dialog, it would be a good idea to change your field name to [pass] or [pword] or something else. Otherwise, you will run into conflicts with the built-in variable [password] when you try to use browser authentication somewhere down the line.Hope this helps.-Dave o--------------- Dave MacLeay --+ o----------- Digital Frontier --+ o--------------- 802.253.8612 --+ o--- dave@digitalfrontier.com --+ Dave MacLeay

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:

back button loses cart (2000) Setting up shop (1997) [WebDNA] sudo WebCatalogCtl stop won't work (2016) For those of you not on the WebCatalog Beta... (1997) incrementing a counter remotely? (1999) Don't tick me off :) [elaspedtime] (1997) psst (1997) HSBC ePayments System (2004) Database (2000) Bug alert! (1997) The code, one more time. (2003) Storebuilder/Webmerchant and Manual CC Processing (2001) Another bug to squash (WebCat2b13 Mac .acgi) (1997) Quit revisited (1997) Modifying order output (1997) Turning a URL into a link (2003) webcatalog [date] bug (1999) Date problems (1997) Shopping carts and reloading pages (1997) ThreadMem ignored? (1998)