Re: Changing the value assigned to a formvariable

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 33471
interpreted = N
texte = > >> >But can I use [formvariables] to retrieve the value and then reassign it > >> >somehow on that same page. I've been trying to do that but can't find a > >> >way to make it work. > >> > >>No, form values are not reassignable -- they are just like other > >>values that come from the visitor's browser, like [ipaddress], they > >>are under the control of the browser, not WebDNA. If you want to > > > >Uh? This is just true for WebCat prior to 4.0, isn't it? > > >Well, obviously if you pass a formvariable named formvar1 into the >page with a value of oldValue, then use this tag at the top of the >page: > >[text]formvar1=newValue[/text] > >... the new default variable hierarchy will make webcat interpret all >occurrences of the [formvar1] tag as newValue, NOT oldValue. But >that's because it's finding the text variable value of formvar1 not >the formvariable value of formvar1. Clearly this is because the new >hierarchy puts text variables on top of formvariables in the >hierarchy. > >To get the true formvariable value, you have to use this code: > >[formvariables name=formvar1&exact=t][value][/formvariables] > >... and the result will still be oldValue, because this code looks >*only* at the existing formvariable values which have not changed, >even though it may LOOK LIKE they have changed if all you use in your >templates are tags like [formvar1] ... > >Confused enough?Not confused by the functions but by the use of the word reassignable. -- ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Ljusa Idéer AB S-211 37 Malmoe Fax +46 40 97 99 77 Sweden http://www.ljusaideer.se------------------------------------------------------------- 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: Changing the value assigned to a formvariable (Christer Olsson 2000)
  2. Re: Changing the value assigned to a formvariable (Kenneth Grome 2000)
  3. Re: Changing the value assigned to a formvariable (Christer Olsson 2000)
  4. Re: Changing the value assigned to a formvariable (Sally Reidy 2000)
  5. Re: Changing the value assigned to a formvariable (WebDNA Support 2000)
  6. Re: Changing the value assigned to a formvariable (Jesse Proudman (Lists Account) 2000)
  7. Re: Changing the value assigned to a formvariable (Sally Reidy 2000)
  8. Re: Changing the value assigned to a formvariable (WebDNA Support 2000)
  9. Re: Changing the value assigned to a formvariable (Jesse Proudman (Lists Account) 2000)
  10. Changing the value assigned to a formvariable (Sally Reidy 2000)
> >> >But can I use [formvariables] to retrieve the value and then reassign it > >> >somehow on that same page. I've been trying to do that but can't find a > >> >way to make it work. > >> > >>No, form values are not reassignable -- they are just like other > >>values that come from the visitor's browser, like [ipaddress], they > >>are under the control of the browser, not WebDNA. If you want to > > > >Uh? This is just true for WebCat prior to 4.0, isn't it? > > >Well, obviously if you pass a formvariable named formvar1 into the >page with a value of oldValue, then use this tag at the top of the >page: > >[text]formvar1=newValue[/text] > >... the new default variable hierarchy will make webcat interpret all >occurrences of the [formvar1] tag as newValue, NOT oldValue. But >that's because it's finding the text variable value of formvar1 not >the formvariable value of formvar1. Clearly this is because the new >hierarchy puts text variables on top of formvariables in the >hierarchy. > >To get the true formvariable value, you have to use this code: > >[formvariables name=formvar1&exact=t][value][/formvariables] > >... and the result will still be oldValue, because this code looks >*only* at the existing formvariable values which have not changed, >even though it may LOOK LIKE they have changed if all you use in your >templates are tags like [formvar1] ... > >Confused enough?Not confused by the functions but by the use of the word reassignable. -- ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Ljusa Idéer AB S-211 37 Malmoe Fax +46 40 97 99 77 Sweden http://www.ljusaideer.se------------------------------------------------------------- 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/ Christer Olsson

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:

Word search (1997) [addlineitems] display (1997) Fwd: Problems with Webcatalog Plug-in (1997) Linux problems (2000) template cache problem (1998) WC TableGrinder (1997) How To (2003) Help! WebCat2 bug (1997) recomend ftp (2001) Banner DNA (1997) NT License trade for Mac (2000) Truncated numbers (2000) unique ascending numbers (2003) WebDNA Life Cycle (was Form POSTing with LONG variable) (2007) Checkboxes and neSKUdata=[blank] (1998) Upgrading old WebCat Database Files (1997) [OT] Change permissions via FTP? (2002) WebCat2: Items xx to xx shown, etc. (1997) Re[3]: Problem with new formvariables (2000) Limit on nested [ShowIf]'s? (1997)