Re: FormVariable

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 23523
interpreted = N
texte = What is your actual setup?i guess i would do a scenario like the following:The person enters the site, a unique cart is created. You have two choises that would be right1. set a cookie [setcookie id=[card]], i sometimes prefer not to this because of all the persons that either disallow cookies or has browsers that dont work, or work well with cookies2. let the value of the card continue to each other page!then you can collect all the info you want about the user, and store it using contextsthe simple way is with the cookies, the best is with letting the id pass from page to pagewhat i normally do ismake a customers.db (to make the shopowner to get more statistics on the use of the shop) with all regular info of the customer like name, address etc maybe even encrypted!The sku of each record in that should be equal to another db which is a db with about the same info as a regular shoppingcart.When the customer is adding products to the basket, it first checks if the order that the customer is working on, is actual processed. If so, the user has allready sent the order, but gone back, (using the back button in the browser), and tried to change the orderwhen the order is processed i close down the database, and move the orderfile to a completed orders folder, so that the user cant change the order, but only make a new order!got anything out of this?A simple thing that might help you work out a solution is:you can allways send webcat variables along to the next page without using forms or doing commands. just like a However if you want it to work around proper way, you might want to add [url] to the variables, like:After this you can allways retrieve that info on the nextpage.tpl by simply adding a [var1] and [var2]Probably the easiest way of passing along information, but at the same time, possible one of the most unsecure!/martin >You are right, I don't want to show them, I want to use them. Perhaps I >stated it >wrong by saying I wanted to use the info for database lookups. I really >just need >to stuff their values into the cart. > >My application is fairly simple, but I need to collect information about the >shopper on one page and then use it two pages later when I have a sku and >can write >to the cart. I'm using textA-textE in the cart to store that shopper info. My >client wants to get the shopper data first, like getting to know you before >presenting the shopping cart page. > >I'm a newbee to webcart....so I appreciate your patience ;-> > >Jan > >Martin Bech wrote: > >> I dont think its possible normal way! >> >> because when using the formvariables it will list all the values, which i >> guess is not what you want! >> >> If you want it to be a lookup, instead of a search context, you should put >> a [lookup db=your.db&lookinfield=yourfield&value=[formvariables][showif >> >>[name]=theName][value][/showif][/formvariables]&returnfield=thereturnfield¬fo >> und=theNotFoundText] >> >> I would considder a search in stead! >> >> /Martin >> >> >I want to use FormVariable to do database lookups....not to list the >> >variables on a page but use the values for processing. Anyone have any >> >insight into this? >> > >> >thanks, >> >Jan Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] [FormVariables] Template (WDD gmail 2013)
  2. [WebDNA] [FormVariables] Template (Stuart Tremain 2013)
  3. Re: Formvariables name matching ( Marko Bernyk 2005)
  4. Re: Formvariables name matching ( Donovan Brooke 2005)
  5. Re: Formvariables name matching ( Stuart Tremain 2005)
  6. Re: Formvariables name matching ( William DeVaul 2005)
  7. Re: Formvariables name matching ( Stuart Tremain 2005)
  8. Formvariables name matching ( William DeVaul 2005)
  9. Re: formvariables exact=F ( Donovan Brooke 2004)
  10. formvariables exact=F ( Donovan Brooke 2004)
  11. Re: [removelineitem] not quite working inside [formvariables] loop (Charles Kline 2001)
  12. Re: [removelineitem] not quite working inside [formvariables] loop (Charles Kline 2001)
  13. Re: [removelineitem] not quite working inside [formvariables] loop (John Peacock 2001)
  14. [removelineitem] not quite working inside [formvariables] loop (Charles Kline 2001)
  15. Re: Spaces in FormVariables (Kenneth Grome 2001)
  16. Re: Spaces in FormVariables (Miguel A. Castaneda 2001)
  17. Spaces in FormVariables (Miguel A. Castaneda 2001)
  18. Re: Spaces in FormVariables (Will Starck 2001)
  19. Re: Formvariables + Netscape + Frame Set = Confusion (Bob Minor 2000)
  20. Re: Formvariables + Netscape + Frame Set = Confusion (Rob Marquardt 2000)
  21. Re: Formvariables + Netscape + Frame Set = Confusion (Rob Marquardt 2000)
  22. Re: Formvariables + Netscape + Frame Set = Confusion (Alan 2000)
  23. Re: Formvariables + Netscape + Frame Set = Confusion (Peter Ostry 2000)
  24. Formvariables + Netscape + Frame Set = Confusion (Alan 2000)
  25. Re: Formvariables + Netscape + Frame Set = Confusion (alan@vci.net 1999)
  26. Re: formvariables question (Kenneth Grome 2000)
  27. formvariables question (Peter Ostry 2000)
  28. Re: Can [formvariables] do this? (Kenneth Grome 2000)
  29. Re: Can [formvariables] do this? (Joseph D'Andrea 2000)
  30. Can [formvariables] do this? (Will Starck 2000)
  31. Re: formvariables not passing (Christopher Mackay 2000)
  32. Re: formvariables not passing (Sally 2000)
  33. Re: formvariables not passing (WebDNA Support 2000)
  34. formvariables not passing (Sally 2000)
  35. [replace] fails with too many formvariables? (Will Starck 2000)
  36. Re: Resetting a Formvariable (John Butler 2000)
  37. Re: Resetting a Formvariable (Glenn Busbin 2000)
  38. Re: Resetting a Formvariable (Glenn Busbin 2000)
  39. Re: Resetting a Formvariable (John Peacock 2000)
  40. Re: Resetting a Formvariable (John Butler 2000)
  41. Re: Resetting a Formvariable (John Butler 2000)
  42. Re: Resetting a Formvariable (Glenn Busbin 2000)
  43. Re: Resetting a Formvariable (Rob Marquardt 2000)
  44. Re: Resetting a Formvariable (Glenn Busbin 2000)
  45. Re: Resetting a Formvariable (Glenn Busbin 2000)
  46. Re: Resetting a Formvariable (Rob Marquardt 2000)
  47. Re: Resetting a Formvariable (WebDNA Support 2000)
  48. Re: Resetting a Formvariable (Anup Setty 2000)
  49. Re: Resetting a Formvariable (Kenneth Grome 2000)
  50. Re: Resetting a Formvariable (Glenn Busbin 2000)
  51. Re: Resetting a Formvariable (John Butler 2000)
  52. Re: Resetting a Formvariable (Glenn Busbin 2000)
  53. Re: Resetting a Formvariable (Glenn Busbin 2000)
  54. Re: Resetting a Formvariable (John Peacock 2000)
  55. Re: Resetting a Formvariable (John Butler 2000)
  56. Re: Resetting a Formvariable (James Howarth 2000)
  57. Resetting a Formvariable (Glenn Busbin 2000)
  58. Formvariable (Nathaniel Hadley 2000)
  59. Re: Formvariable (Paul Fowler 2000)
  60. Re: Changing the value assigned to a formvariable (Christer Olsson 2000)
  61. Re: Changing the value assigned to a formvariable (Kenneth Grome 2000)
  62. Re: Changing the value assigned to a formvariable (Christer Olsson 2000)
  63. Re: Changing the value assigned to a formvariable (Sally Reidy 2000)
  64. Re: Changing the value assigned to a formvariable (WebDNA Support 2000)
  65. Re: Changing the value assigned to a formvariable (Jesse Proudman (Lists Account) 2000)
  66. Re: Changing the value assigned to a formvariable (Sally Reidy 2000)
  67. Re: Changing the value assigned to a formvariable (WebDNA Support 2000)
  68. Re: Changing the value assigned to a formvariable (Jesse Proudman (Lists Account) 2000)
  69. Changing the value assigned to a formvariable (Sally Reidy 2000)
  70. Re: formvariable funkyness (Bo Hess 2000)
  71. formvariable funkyness (Bo Hess 2000)
  72. Formvariable Heirarchy (Brian Rhoten 2000)
  73. Re: Proposed FormVariables hierarchy (John Butler 2000)
  74. Re: Proposed FormVariables hierarchy (John Peacock 2000)
  75. Re: Proposed FormVariables hierarchy (Nicolas Verhaeghe 2000)
  76. Re: Proposed FormVariables hierarchy (Kenneth Grome 2000)
  77. Re: Proposed FormVariables hierarchy (John Peacock 2000)
  78. Re: Proposed FormVariables hierarchy (Pat McCormick 2000)
  79. Re: Proposed FormVariables hierarchy (Kenneth Grome 2000)
  80. Re: Proposed FormVariables hierarchy (GHulbert@smithmicro.com 2000)
  81. Re: Proposed FormVariables hierarchy (Thomas Wedderburn-Bisshop 2000)
  82. Re: Proposed FormVariables hierarchy (Michael Winston 2000)
  83. Re: Proposed FormVariables hierarchy (Kenneth Grome 2000)
  84. Proposed FormVariables hierarchy (GHulbert@smithmicro.com 2000)
  85. Re: Re[4]: Problem with new formvariables (Thomas Wedderburn-Bisshop 2000)
  86. Re: Re[4]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  87. Re[2]: Problem with new formvariables (Christer Olsson 2000)
  88. Re: Re[4]: Problem with new formvariables (Thomas Wedderburn-Bisshop 2000)
  89. Re: Re[4]: Problem with new formvariables (Thomas Wedderburn-Bisshop 2000)
  90. Re[5]: Problem with new formvariables (jpeacock@univpress.com 2000)
  91. Re[3]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  92. Re[3]: Re[3]: Problem with new formvariables (Kenneth Grome 2000)
  93. Re[4]: Problem with new formvariables (Kenneth Grome 2000)
  94. Re[2]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  95. Re[4]: Problem with new formvariables (jpeacock@univpress.com 2000)
  96. Re[2]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  97. Re[4]: Problem with new formvariables (Sam Lewis 2000)
  98. Re: Re[4]: Problem with new formvariables (Rob Marquardt 2000)
  99. Re[2]: Re[3]: Problem with new formvariables (Kenneth Grome 2000)
  100. Re: Re[2]: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  101. Re: Re[2]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  102. Re[3]: Problem with new formvariables (Michael Winston 2000)
  103. Re: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  104. Re: Re[3]: Problem with new formvariables (Mike Davis 2000)
  105. Re: Re[2]: Problem with new formvariables (Grant Hulbert 2000)
  106. Re: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  107. Re: Re[3]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  108. Re[3]: Problem with new formvariables (Grant Hulbert 2000)
  109. Re: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  110. Re: Re[3]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  111. Re: Re[2]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  112. Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  113. Re[3]: Problem with new formvariables (Michael Winston 2000)
  114. Re[2]: Problem with new formvariables (Grant Hulbert 2000)
  115. Re[2]: Problem with new formvariables (Joseph D'Andrea 2000)
  116. Re[2]: Problem with new formvariables (jpeacock@univpress.com 2000)
  117. Re: Problem with new formvariables (Kenneth Grome 2000)
  118. Problem with new formvariables (Nicolas Verhaeghe 2000)
  119. Re: [Feature Request] Stronghold security variables that cannot beforce as formvariables (John Butler 2000)
  120. Re: Formvariables and Sendmail? (Anup Setty 2000)
  121. Re: Sendmail and Formvariables (Fritz Gifts and Collectibles 2000)
  122. Formvariables and Sendmail? (Fritz Gifts and Collectibles 2000)
  123. Re: Formvariable won't update (Nicolas Verhaeghe 1999)
  124. Re: Formvariable won't update ( 1999)
  125. Re: Formvariable won't update (Eric Ridgley 1999)
  126. Re: Formvariable won't update (Anup Setty 1999)
  127. Formvariable won't update (Nicolas Verhaeghe 1999)
  128. Re: can I get formvariables for an include? (John Jakovich 1999)
  129. can I get formvariables for an include? (Olin Lagon 1999)
  130. Re: [spawn] and [formvariables] (Grant Hulbert 1999)
  131. [spawn] and [formvariables] (tcrist@digitalfrontier.com 1999)
  132. Re: FormVariable (Martin Bech 1999)
  133. Re: FormVariable (Jan Kinzler 1999)
  134. Re: FormVariable (Martin Bech 1999)
  135. FormVariable (Jan Kinzler 1999)
  136. Re: [text] doesn't change [formvariables] (PCS Technical Support 1999)
  137. [text] doesn't change [formvariables] (Kenneth Grome 1999)
  138. Re(7): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  139. Re(2): Re(4): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  140. Re(9): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  141. Re(9): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  142. Re: Re(4): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (Will Starck 1998)
  143. Re(8): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  144. Re(6): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  145. Re(7): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  146. Re(8): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  147. Re(5): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  148. Re(6): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  149. Re(7): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  150. Re(5): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  151. Re(4): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (Kenneth Grome 1998)
  152. Re(6): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  153. Re(5): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  154. Re(4): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (Kimberly D. Wyrick 1998)
  155. Re(4): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  156. Re(3): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  157. Re(2): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  158. Re: Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (l.bache@interacti-system.fr (Laurent Bache) 1998)
  159. Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (Michael Winston 1998)
  160. Re: Terry's formvariables tip (Jim V 1998)
  161. Terry's formvariables tip (Dan Tryon 1998)
  162. Re: shownext problems & formvariables (Terry Wilson 1998)
  163. Re: addlineitems within formvariable loop (Grant Hulbert 1998)
  164. addlineitems within formvariable loop (Tom Leitner 1998)
  165. Re: [sendmail] and [formvariables] (Kenneth Grome 1997)
  166. Re: [sendmail] and [formvariables] (Grant Hulbert 1997)
  167. [sendmail] and [formvariables] (grichter@panavise.com (Gary Richter) 1997)
  168. [formvariables] ( List)
What is your actual setup?i guess i would do a scenario like the following:The person enters the site, a unique cart is created. You have two choises that would be right1. set a cookie [setcookie id=[card]], i sometimes prefer not to this because of all the persons that either disallow cookies or has browsers that dont work, or work well with cookies2. let the value of the card continue to each other page!then you can collect all the info you want about the user, and store it using contextsthe simple way is with the cookies, the best is with letting the id pass from page to pagewhat i normally do ismake a customers.db (to make the shopowner to get more statistics on the use of the shop) with all regular info of the customer like name, address etc maybe even encrypted!The sku of each record in that should be equal to another db which is a db with about the same info as a regular shoppingcart.When the customer is adding products to the basket, it first checks if the order that the customer is working on, is actual processed. If so, the user has allready sent the order, but gone back, (using the back button in the browser), and tried to change the orderwhen the order is processed i close down the database, and move the orderfile to a completed orders folder, so that the user cant change the order, but only make a new order!got anything out of this?A simple thing that might help you work out a solution is:you can allways send webcat variables along to the next page without using forms or doing commands. just like a However if you want it to work around proper way, you might want to add
[url] to the variables, like:[url]myName[/url]&var2=[url]MyAddress[/url]>After this you can allways retrieve that info on the nextpage.tpl by simply adding a [var1] and [var2]Probably the easiest way of passing along information, but at the same time, possible one of the most unsecure!/martin >You are right, I don't want to show them, I want to use them. Perhaps I >stated it >wrong by saying I wanted to use the info for database lookups. I really >just need >to stuff their values into the cart. > >My application is fairly simple, but I need to collect information about the >shopper on one page and then use it two pages later when I have a sku and >can write >to the cart. I'm using textA-textE in the cart to store that shopper info. My >client wants to get the shopper data first, like getting to know you before >presenting the shopping cart page. > >I'm a newbee to webcart....so I appreciate your patience ;-> > >Jan > >Martin Bech wrote: > >> I dont think its possible normal way! >> >> because when using the formvariables it will list all the values, which i >> guess is not what you want! >> >> If you want it to be a lookup, instead of a search context, you should put >> a [lookup db=your.db&lookinfield=yourfield&value=[formvariables][showif >> >>[name]=theName][value][/showif][/formvariables]&returnfield=thereturnfield¬fo >> und=theNotFoundText] >> >> I would considder a search in stead! >> >> /Martin >> >> >I want to use FormVariable to do database lookups....not to list the >> >variables on a page but use the values for processing. Anyone have any >> >insight into this? >> > >> >thanks, >> >Jan Martin Bech

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:

encrypt but with normal characters for result? (2005) RE: 2.1 pricing? (1998) 4.5 Upgrade (2003) New Mac Emailer... (1997) Security - 2 (1999) Netscape v. IE (1997) Privacy Issue (LEGIT QUESTION) (2003) WebCatalog Work (2001) Email Not Being Sent (2004) [trim]?! (2004) mac hack (1997) using showpage and showcart commands (1996) embedded search vs. URL (2004) [convertchars] limits (1998) RE: [WebDNA] tcp connect is slow...any ways to speed it up? (2008) RE: Sum of Quantities (1997) Merchant account (1998) Hard Questions ? (1997) [math] variable question (1997) WebCat2b12 - nesting [tags] (1997)