Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing)

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 34993
interpreted = N
texte = But John P. ... under certain conditions, forms inputs named after headers (and submitted via form) is enough to get them into the header slots (like shipVia, etc. in SM sample stores) SO there is another way... the way that newer users tend to rely on without even knowing how it works... But still convenient as heck ;-) Maybe you could give us a comprehensive overview of those conditions...?-John B.John Peacock wrote:> Steven Jarvis wrote: > > Okay, just to make sure I understand this, when the customer enters data in > > the form and submits it and the form field was styled: > > > > > > > > where [Header14] was empty, whatever data he submitted would be placed in > > [Header14] of his cart, yes? > > > > No, you don't have it at all. If you are in an orderfile context, > [Header14] will display what is currently in the current cart's Header14 > field. If you want to save something to a header field, you need to use > either: > [SetHeader] > or [SetLineItem] > or [AddLineItem] > > Wait, some of you are going to yell, how can you set a header field by > setting a line item? Look at the 4.x docs; when setting or adding a > new line item, if you include any header field in the context, it will > also be updated. Very useful, methinks... > > If you want to capture a user's choice from a list, or an input field, > and stuff it into the header, use something like this on the _next_ > page: > > [SetHeader cart=[cart]&db=my.db]Header9=[_formvar][/SetHeader] > > where _formvar is any form variable passed from the previous page. > > HTH > > John Peacock ------------------------------------------------------------- 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://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing) (John Peacock 2000)
  2. Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing) (John Butler 2000)
  3. Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing) (John Butler 2000)
  4. Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing) (John Peacock 2000)
  5. Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing) (John Butler 2000)
  6. Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing) (John Butler 2000)
  7. Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing) (John Peacock 2000)
But John P. ... under certain conditions, forms inputs named after headers (and submitted via form) is enough to get them into the header slots (like shipVia, etc. in SM sample stores) SO there is another way... the way that newer users tend to rely on without even knowing how it works... But still convenient as heck ;-) Maybe you could give us a comprehensive overview of those conditions...?-John B.John Peacock wrote:> Steven Jarvis wrote: > > Okay, just to make sure I understand this, when the customer enters data in > > the form and submits it and the form field was styled: > > > > > > > > where [Header14] was empty, whatever data he submitted would be placed in > > [Header14] of his cart, yes? > > > > No, you don't have it at all. If you are in an orderfile context, > [Header14] will display what is currently in the current cart's Header14 > field. If you want to save something to a header field, you need to use > either: > [setheader] > or [setlineitem] > or [addlineitem] > > Wait, some of you are going to yell, how can you set a header field by > setting a line item? Look at the 4.x docs; when setting or adding a > new line item, if you include any header field in the context, it will > also be updated. Very useful, methinks... > > If you want to capture a user's choice from a list, or an input field, > and stuff it into the header, use something like this on the _next_ > page: > > [SetHeader cart=[cart]&db=my.db]Header9=[_formvar][/SetHeader] > > where _formvar is any form variable passed from the previous page. > > HTH > > John Peacock ------------------------------------------------------------- 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://search.smithmicro.com/ John Butler

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:

Search Question (2000) [WriteFile] problems (1997) Looking for a Manual (1997) Appending space (1998) WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997) do you have a webcatalog tool you want to sell? (1999) Re:Emailer setup (1997) page redirect in webDNA (1997) [protect admin] (1997) WebCatalog/Mac 2.1b2 New Features (1997) Re:quit command on NT (1997) WebCat2b13MacPlugIn - More limits on [include] (1997) WebCatalog2 for NT Beta Request (1997) Date Question (2002) Checkboxes (1997) InSecureTextVariables.... (2000) PCS Customer submissions ? (1997) Multiple prices (1997) Extended [ConvertChars] (1997) [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (2010)