Re: REPLACE problem

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 34068
interpreted = N
texte = Glenn,Once you fully get what WebDNA Support is saying (do make reeeal simple test templates to teach yourself one phenomenon at a time, as you go), then realize you can up the complexity a bit and then keep it all on one page as you said you wanted. You still have to submit the form so the variable values will be available on the next page, but the next page can be the same page where the form is.Here's a very simple example: *********** this is page1.tpl [hideif [URL][a][/URL]=b]
The var '__CommonName' has not yet been given a value, so it displays as [__CommonName].

__CommonName=[__CommonName] [/hideif][showif [URL][a][/URL]=b] Here we are again on this same page, but the conditions are different now. the variables 'a' and '__CommonName' both have been given a value. (If you did not type anything into the text input then '__CommonName' now has the value of *nothing* (called the null string), which *is* still a value.

__CommonName=[__CommonName]
a=[a][replace db=my.db&eqSKUdatarq=[url][sku][/url]]commonname=[url][__commonname][/url][/replace][/showif] ************-JohnWebDNA Support wrote:> >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? > > > 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. > ------------------------------------------------------------- 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)
Glenn,Once you fully get what WebDNA Support is saying (do make reeeal simple test templates to teach yourself one phenomenon at a time, as you go), then realize you can up the complexity a bit and then keep it all on one page as you said you wanted. You still have to submit the form so the variable values will be available on the next page, but the next page can be the same page where the form is.Here's a very simple example: *********** this is page1.tpl [hideif [url][a][/URL]=b]
[!]--Later you can figure out how to give this input a preset value or not - using showif or hideif--[/!]>
The var '__CommonName' has not yet been given a value, so it displays as [__CommonName].

__CommonName=[__CommonName] [/hideif][showif [url][a][/URL]=b] Here we are again on this same page, but the conditions are different now. the variables 'a' and '__CommonName' both have been given a value. (If you did not type anything into the text input then '__CommonName' now has the value of *nothing* (called the null string), which *is* still a value.

__CommonName=[__CommonName]
a=[a][replace db=my.db&eqSKUdatarq=[url][sku][/url]]commonname=[url][__commonname][/url][/replace][/showif] ************-JohnWebDNA Support wrote:> >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? > > > 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. > ------------------------------------------------------------- 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:

WebCat2: Formulas.db question (1997) Problems getting parameters passed into email. (1997) [math] show=F exists? (1997) oops private message leaked into talk list (1997) Signal Raised Error (1997) Associative lookup style? (1997) Authenticate (1997) [BoldWords] WebCat.acgib15Mac (1997) [WebDNA] Limits? (2009) Fun with dates (1997) Deleting Orders (1997) input type=file has no value? (2003) To use GREP to boldface text (2003) WebTen? (1997) WebCat 2.1beta etc (1997) [Solved? - with code] catching WebDNA error messages (2003) Rollovers (1999) [WebDNA] Mailing list failure !!! (2019) [countWords]? (1997) MOOOOOO (2000)