Re: [WebDNA] unused database fields. . . .

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111398
interpreted = N
texte = Hi Rich! if you append fields that do not exist in a form, something = like &firstname=3D[url][firstname][/url] then =93[firstname]=94 (with = the brackets) will be added to the database. WebDNA is just expecting = the field content, and since this one does not exist, then the code = [firstname] that should be replaced by the field content will appear = instead. This is normal behaviour. - chris On Jun 20, 2014, at 15:58, Rich Kwas wrote: > Hi Donocan. >=20 > Let me explain it again.............. >=20 > A somewhat simple form on a website where ad payment information is = entered...... > CC payments are handled manually, so just info is gathered..... >=20 > Here is the beginning of the append to the database snippet: > [append = db=3D^/membership/advertising.db]uniqueID=3D[cart]&submit_date=3D[date]&su= bmit_time=3D[time]&submit_ip=3D[ipaddress]&firstname=3D[url][firstname][/u= rl]&lastname=3D[url][lastname][/url]&ad_name=3D[url]ad_name[/url][/append]= >=20 > firstname & lastname will "not" be used anymore on the form, but they = are being left in advertising.hdr since they may come to life again = sometime in the future.... >=20 > When form info is submitted and appended to advertising.db the 2 = unused fields (no longer in the form) are having their field names = written into the database. >=20 > [firstname] (the field name with the brackets) > [lastname] (the field name with the brackets) > ad_name information is being written just fine >=20 >=20 >=20 > I'm guessing I should just not have these old field names in the = append part? > (I should have thought of that earlier..) >=20 >=20 > BUT > why would the field names get written if they are nowhere on the form = but still appear in the append part and are still in advertising.hdr >=20 >=20 >=20 >=20 > On Thursday, June 19, 2014 10:29 AM, Donovan Brooke = wrote: >=20 >=20 >=20 > On Jun 19, 2014, at 8:00 AM, Rich Kwas = wrote: >=20 > > Added some new fields to an existing database. > > on the website information is being entered into a payment form. > >=20 > > Some of the existing field names will not be used anymore in an = upcoming update. > > These unused fields will no longer appear on the form. > > BUT these old fields unused field names are being written into the = database. > >=20 > > example: > > [type_of_ad] > > [travel] > > [city_based_in] > >=20 > > Why would this be happening? >=20 >=20 > Undefined variables output as raw text. >=20 >=20 >=20 > > I'm pretty sure I have unused fields in other sites but never had = this happen until this project. > >=20 > > Narrowed down all other possibilities causing this and its just the = unused fields being written this way. > >=20 > > These unused fields are still being "appended" to the existing db, = even though they don't appear on the form anymore and there is no actual = data to append.=20 > >=20 > > Should these field names be written into the database if the field = doesn't appear on the form BUT that field name is still in the append = code? > >=20 > >=20 > > Here is how two of the unused fields are being appended: > > firstname > > lastname > >=20 > > [append = db=3D^/membership/advertising.db]uniqueID=3D[cart]&submit_date=3D[date]&su= bmit_time=3D[time]&submit_ip=3D[ipaddress]&firstname=3D[url][firstname][/u= rl]&lastname=3D[url][lastname][/url][/append] > >=20 > > firstname & lastname do not appear on this form anywhere. >=20 >=20 >=20 > Rich, maybe restate your question clearer. I=92m confused :-) >=20 > Sincerely, > Donovan >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] unused database fields. . . . (Rich Kwas 2014)
  2. Re: [WebDNA] unused database fields. . . . (christophe.billiottet@webdna.us 2014)
  3. Re: [WebDNA] unused database fields. . . . (Rich Kwas 2014)
  4. Re: [WebDNA] unused database fields. . . . (Donovan Brooke 2014)
  5. [WebDNA] unused database fields. . . . (Rich Kwas 2014)
Hi Rich! if you append fields that do not exist in a form, something = like &firstname=3D[url][firstname][/url] then =93[firstname]=94 (with = the brackets) will be added to the database. WebDNA is just expecting = the field content, and since this one does not exist, then the code = [firstname] that should be replaced by the field content will appear = instead. This is normal behaviour. - chris On Jun 20, 2014, at 15:58, Rich Kwas wrote: > Hi Donocan. >=20 > Let me explain it again.............. >=20 > A somewhat simple form on a website where ad payment information is = entered...... > CC payments are handled manually, so just info is gathered..... >=20 > Here is the beginning of the append to the database snippet: > [append = db=3D^/membership/advertising.db]uniqueID=3D[cart]&submit_date=3D[date]&su= bmit_time=3D[time]&submit_ip=3D[ipaddress]&firstname=3D[url][firstname][/u= rl]&lastname=3D[url][lastname][/url]&ad_name=3D[url]ad_name[/url][/append]= >=20 > firstname & lastname will "not" be used anymore on the form, but they = are being left in advertising.hdr since they may come to life again = sometime in the future.... >=20 > When form info is submitted and appended to advertising.db the 2 = unused fields (no longer in the form) are having their field names = written into the database. >=20 > [firstname] (the field name with the brackets) > [lastname] (the field name with the brackets) > ad_name information is being written just fine >=20 >=20 >=20 > I'm guessing I should just not have these old field names in the = append part? > (I should have thought of that earlier..) >=20 >=20 > BUT > why would the field names get written if they are nowhere on the form = but still appear in the append part and are still in advertising.hdr >=20 >=20 >=20 >=20 > On Thursday, June 19, 2014 10:29 AM, Donovan Brooke = wrote: >=20 >=20 >=20 > On Jun 19, 2014, at 8:00 AM, Rich Kwas = wrote: >=20 > > Added some new fields to an existing database. > > on the website information is being entered into a payment form. > >=20 > > Some of the existing field names will not be used anymore in an = upcoming update. > > These unused fields will no longer appear on the form. > > BUT these old fields unused field names are being written into the = database. > >=20 > > example: > > [type_of_ad] > > [travel] > > [city_based_in] > >=20 > > Why would this be happening? >=20 >=20 > Undefined variables output as raw text. >=20 >=20 >=20 > > I'm pretty sure I have unused fields in other sites but never had = this happen until this project. > >=20 > > Narrowed down all other possibilities causing this and its just the = unused fields being written this way. > >=20 > > These unused fields are still being "appended" to the existing db, = even though they don't appear on the form anymore and there is no actual = data to append.=20 > >=20 > > Should these field names be written into the database if the field = doesn't appear on the form BUT that field name is still in the append = code? > >=20 > >=20 > > Here is how two of the unused fields are being appended: > > firstname > > lastname > >=20 > > [append = db=3D^/membership/advertising.db]uniqueID=3D[cart]&submit_date=3D[date]&su= bmit_time=3D[time]&submit_ip=3D[ipaddress]&firstname=3D[url][firstname][/u= rl]&lastname=3D[url][lastname][/url][/append] > >=20 > > firstname & lastname do not appear on this form anywhere. >=20 >=20 >=20 > Rich, maybe restate your question clearer. I=92m confused :-) >=20 > Sincerely, > Donovan >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us christophe.billiottet@webdna.us

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:

RequiredFields template (1997) & not allowed in db by definition? (1999) Authenticate (1997) Fun with dates (1997) [WebDNA] OT: Issue with some clouds (2009) WebCommerce: Folder organization ? (1997) Dark Horse Comics success story (1997) Num Sort Descending (2004) Shipping rate x Quantity solution needed (2000) Showing unopened cart (1997) Web Developer Product Awards (1997) webcat running as www, should that be webstar for use withwebstar? (2002) Emailer not working (1998) credit card authorization question (1997) all records returned. (1997) vars (2000) Paradata/Moneris Gateway (2005) WebCat2: Formulas.db question (1997) the dreaded unitShipCost (2003) New Command prefs ... (1997)