Re: REPLACE problem

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 34065
interpreted = N
texte = >Yes. I'd like to be able to change anything on the page. That's why I put >the form variables with each field. I put the Replace at the bottom of the >page so that I can use it for ALL of the fields. Is this not a good idea?There's a basic concept here: if you put HTMl form input fields on a page, you absolutely cannot put WebDNA further down that *same* page which is expecting to use the values of those input fields. HTML browsers and the web just don't work that way, because the form variables your browser submits to the web server won't show up until the *next* page, whatever your
page is. WebDNA executes on the server side, not in the browser.Make yourself a real simple pair of templates, where you display the value of [__commonname] on a page which has a form on it, and then on the next page also put [__commonname] and you'll see that the value is only available on the next page.There is nothing wrong with [replace], you are just telling it to literally put the text [__commonname] into a field. If [__commonname] had some value in it at the time the [replace] was executed, then whatever that value is would being going into your database.Also it's a good idea to start using the following to debug what the values are of your incoming form variables, so you can see what's really happening on a page:[FormVariables] [name] = [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:

    
  1. Re: REPLACE problem (John Butler 2000)
  2. Re: REPLACE problem (WebDNA Support 2000)
  3. Re: REPLACE problem (Glenn Busbin 2000)
  4. Re: REPLACE problem (Glenn Busbin 2000)
  5. Re: REPLACE problem (WebDNA Support 2000)
  6. REPLACE problem (Glenn Busbin 2000)
  7. Re: replace problem (Kenneth Grome 1999)
  8. Re: replace problem (listas 1999)
  9. Re: replace problem (Kenneth Grome 1999)
  10. Re: replace problem (listas 1999)
  11. Re: replace problem (Will Starck 1999)
  12. Re: replace problem (listas 1999)
  13. Re: replace problem (Will Starck 1999)
  14. replace problem (listas 1999)
>Yes. I'd like to be able to change anything on the page. That's why I put >the form variables with each field. I put the Replace at the bottom of the >page so that I can use it for ALL of the fields. Is this not a good idea?There's a basic concept here: if you put HTMl form input fields on a page, you absolutely cannot put WebDNA further down that *same* page which is expecting to use the values of those input fields. HTML browsers and the web just don't work that way, because the form variables your browser submits to the web server won't show up until the *next* page, whatever your page is. WebDNA executes on the server side, not in the browser.Make yourself a real simple pair of templates, where you display the value of [__commonname] on a page which has a form on it, and then on the next page also put [__commonname] and you'll see that the value is only available on the next page.There is nothing wrong with [replace], you are just telling it to literally put the text [__commonname] into a field. If [__commonname] had some value in it at the time the [replace] was executed, then whatever that value is would being going into your database.Also it's a good idea to start using the following to debug what the values are of your incoming form variables, so you can see what's really happening on a page:[formvariables] [name] = [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:

New Command prefs ... (1997) PSC recommends what date format yr 2000??? (1997) PROBLEMS WITH WEBCAT LINUX (2000) [format 40s]text[/format] doesn't work (1997) StoreBuilder Shopping Cart (2000) Convertchars bug? (2003) system crashes, event log (1997) RequiredFields template (1997) This list needs a digest: rant, rave... (1997) WebCatalog can't find database (1997) [ShowIf] and empty fields (1997) URGENT - CPU usage OSXS (2001) [url] (1997) useful guidelines =] vs !] (2007) WebCat2b15MacPlugin - [protect] (1997) WebDNA 5.1 and Mac OS X Server v10.3 - Working ??? (2003) How can I Add several Items into the cart at once? (1997) format problem on NT? (1997) I have observed and I am gone. (1998) Multiple Pulldowns (1997)