Re: orderfile headers (was: 2nd Request for help/adviceonvariable pricing)
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 35007
interpreted = N
texte = John P., you must have misunderstood my last post in this thread.Or at least one thing for certain (I am 98% certain on this)-to...twiddle the header values without adding or setting a line item...there is *ANOTHER WAY* other than- ...you need to use the [setheader] context....I don't have enough experience to describe all the ways it can work, but for sure under these conditions:You have an HTML form within an orderfile context (implicit or explicit). That form has an input field named after one of the orderfile header values. You input a value for that input field. You submit the form which goes to another page which is also within an orderfile context. Now *presto* the orderfile's header matching that input name has been updated with your input value.I haven't used tea room since webcat 2, but that old tea room relied heavily on updating orderfile header values this way. I bet they are still using this method alot! It is convenient and if webcat is set up for it to work, then why hassle using other means unless you need to? Most beginners just want to get their stuff selling NOW! And webcat designers intended that people could get a store working without even having to know alot of what was really happening under the hood, and without having (in as many cases as possible) to learn how to do alot of custom coding/tweaking.What I was asking you is if you could explain what other conditions (other than what I descibe above) allow orderfile header values to get updated automagically via simple innocent HTML forms inputs named after orderfile header values. Maybe you don't know... ? Maybe there are no other conditions that allow the phenomena. If so, then both the form page and form's action page both have to be within orderfile contexts (implicitly by virtue of a webcat shopping command, or else explicity by virtue of [orderfile...]...[/orderfile]) and the input name must match an orderfile header you want to update upon form submit.-John B.John Peacock wrote:> I was discussing the context versions, but the command version works in > a like manner. Any time you use command=add to insert a line item (with > either a link or a form), you can also update the header values. There > is no corresponding setlineitem command. If you want to twiddle the > header values without adding or setting a line item, you need to use the > [setheader] context. > > HTH > > John Peacock > > John Butler wrote: > > > > 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. > > ------------------------------------------------------------- > 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/ ------------------------------------------------------------- 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:
John P., you must have misunderstood my last post in this thread.Or at least one thing for certain (I am 98% certain on this)-to...twiddle the header values without adding or setting a line item...there is *ANOTHER WAY* other than- ...you need to use the [setheader] context....I don't have enough experience to describe all the ways it can work, but for sure under these conditions:You have an HTML form within an orderfile context (implicit or explicit). That form has an input field named after one of the orderfile header values. You input a value for that input field. You submit the form which goes to another page which is also within an orderfile context. Now *presto* the orderfile's header matching that input name has been updated with your input value.I haven't used tea room since webcat 2, but that old tea room relied heavily on updating orderfile header values this way. I bet they are still using this method alot! It is convenient and if webcat is set up for it to work, then why hassle using other means unless you need to? Most beginners just want to get their stuff selling NOW! And webcat designers intended that people could get a store working without even having to know alot of what was really happening under the hood, and without having (in as many cases as possible) to learn how to do alot of custom coding/tweaking.What I was asking you is if you could explain what other conditions (other than what I descibe above) allow orderfile header values to get updated automagically via simple innocent HTML forms inputs named after orderfile header values. Maybe you don't know... ? Maybe there are no other conditions that allow the phenomena. If so, then both the form page and form's action page both have to be within orderfile contexts (implicitly by virtue of a webcat shopping command, or else explicity by virtue of [orderfile...]...[/orderfile]) and the input name must match an orderfile header you want to update upon form submit.-John B.John Peacock wrote:> I was discussing the context versions, but the command version works in > a like manner. Any time you use command=add to insert a line item (with > either a link or a form), you can also update the header values. There > is no corresponding setlineitem command. If you want to twiddle the > header values without adding or setting a line item, you need to use the > [setheader] context. > > HTH > > John Peacock > > John Butler wrote: > > > > 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. > > ------------------------------------------------------------- > 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/ ------------------------------------------------------------- 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:
real beginner stumped (2000)
Nesting format tags (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
WebCat2.0 [format thousands .0f] no go (1997)
Non-Cart Files in Shopping Cart Folder (1997)
THANKS (1997)
Authenticate (1997)
Create Folder Question... (2000)
Encrypted Templates Serving as Text (2000)
Virtual hosting and webcatNT (1997)
case number with spaces. (2000)
RE: [WebDNA] WebDNA Hosts (2009)
How true is this? (1999)
WebCatalog2 Feature Feedback (1996)
WebCat2b15MacPlugin - [protect] (1997)
[WebDNA] reCAPTCHA and WebDNA (2010)
[WebDNA] Bug in [thisurlplusget] on v7 (2011)
TCPconnect & XML (2008)
emailer setup (1997)
FYI: Apache Module perchild (2002)