Re: Changing the value assigned to a formvariable
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 33396
interpreted = N
texte = >Yes, I can work around this, but what gives here? You can't change >formvariable values with a text assignment statement? Or is there another >way I should be doing it?Form variables are a completely different namespace from text variables. Form variables are not changeable, because they come from the remote browser, analogous to the remote browser's ip address and cookies and such. You should use a different variable name for the text variables, or else be more explicit about which namespace you're pulling from.[x] is considered 'lazy syntax' because it could be a value from a [text], [math], or [formvariables] context, so you can explicitly retrieve variables from the different namespaces like so:[math]x[/math] [text]x[/text] [formvariables name=x&exact=t][value][/formvariables]Technical Support ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive, #380 | ------------------------- San Diego, CA 92127 | Software & Site Development WebCatalog Support: (858) 675-0632 | http://www.smithmicro.com Fax: (858) 675-0372 **********************************------------------------------------------------------------- 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:
>Yes, I can work around this, but what gives here? You can't change >formvariable values with a text assignment statement? Or is there another >way I should be doing it?Form variables are a completely different namespace from text variables. Form variables are not changeable, because they come from the remote browser, analogous to the remote browser's ip address and cookies and such. You should use a different variable name for the text variables, or else be more explicit about which namespace you're pulling from.[x] is considered 'lazy syntax' because it could be a value from a [text], [math], or [formvariables] context, so you can explicitly retrieve variables from the different namespaces like so:[math]x[/math] [text]x[/text] [formvariables name=x&exact=t][value][/formvariables]Technical Support ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive, #380 | ------------------------- San Diego, CA 92127 | Software & Site Development WebCatalog Support: (858) 675-0632 | http://www.smithmicro.com Fax: (858) 675-0372 **********************************------------------------------------------------------------- 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/
WebDNA Support
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:
[WebDNA] Timer (2009)
PLEASE REMOVE MY EMAIL ADDRESS (1997)
Refering page (1998)
error: Too many nested [xxx] contexts (1997)
Re:no [search] with NT (1997)
[OT] Accepting Credit Cards Online (1999)
[WebDNA] Error 500 with SUMM=T (2017)
cc auth with [purchase] (1998)
Bug Report, maybe (1997)
Re:no [search] with NT (1997)
PCS Frames (1997)
Sendmail (1998)
remove line item (2000)
no global [username] or [password] displayed ... (1997)
[URL] around a [sendmail] recipient? (2000)
Next (1997)
Hairy Shipping Monster (2006)
Weighting of grouped results possible? (was: grouping fieldsquestion) (1998)
Calculating multiple shipping... (1997)
upgrade? (1997)