Re: SHOWIF/HIDEIF empty fields

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 61904
interpreted = N
texte = Gary Krockover wrote: > > Correct, my mistake - it's not the landing page on forms but when > recalling a pre-populated form, such as in the case where the visitor > missed a required field and I've redirected them back to the form while > checking for existing values in a custom "required fields" situation. > > Example, visitor fills in form, that appends to a db but they missed a > field. I redirect them back to the form and repopulate the form from > what they did fill in. .... > but I'm still checking to see if it > equals [raw][field][/raw], either there or when repopulating the form. It should, but remember to put the comparasion string in the right order: [SHOWIF/HIDEIF [RAW][FIELD][/RAW]=[FIELD]] or possibly: [SHOWIF/HIDEIF [RAW][FIELD][/RAW]=[URL][FIELD][/URL]] You really ought to do a double check with both that one and [SHOWIF/HIDEIF ![URL][FIELD][/URL]] An unfilled form field should be passed on as a blank rather tha remain undefined although that doesn't always happen. Another method is to have each field prefilled in with a dummy value:
and then check for that value. Not foolproof unfortunately Or you can do it the old fashioned way with JavaScript of course. If you want absolute max safety, you can easily combine all of those methods. Then only the absolute best of fools can manage to mess it up. Frank Nordberg http://www.musicaviva.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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: SHOWIF/HIDEIF empty fields ( Terry Wilson 2005)
  2. Re: SHOWIF/HIDEIF empty fields ( Kenneth Grome 2005)
  3. Re: SHOWIF/HIDEIF empty fields ( Donovan Brooke 2005)
  4. Re: SHOWIF/HIDEIF empty fields ( Lester 2005)
  5. Re: SHOWIF/HIDEIF empty fields ( Donovan Brooke 2005)
  6. Re: SHOWIF/HIDEIF empty fields ( Frank Nordberg 2005)
  7. Re: SHOWIF/HIDEIF empty fields ( Stuart Tremain 2005)
  8. Re: SHOWIF/HIDEIF empty fields ( Kenneth Grome 2005)
  9. Re: SHOWIF/HIDEIF empty fields ( Bob Minor 2005)
  10. Re: SHOWIF/HIDEIF empty fields ( "WebDna @ Inkblot Media" 2005)
  11. Re: SHOWIF/HIDEIF empty fields ( Kenneth Grome 2005)
  12. Re: SHOWIF/HIDEIF empty fields ( Donovan Brooke 2005)
  13. Re: SHOWIF/HIDEIF empty fields -- OOPS ( Gary Krockover 2005)
  14. Re: SHOWIF/HIDEIF empty fields ( Gary Krockover 2005)
  15. Re: SHOWIF/HIDEIF empty fields ( Kenneth Grome 2005)
  16. Re: SHOWIF/HIDEIF empty fields ( Stuart Tremain 2005)
  17. Re: SHOWIF/HIDEIF empty fields ( Gary Krockover 2005)
  18. Re: SHOWIF/HIDEIF empty fields ( Stuart Tremain 2005)
  19. Re: SHOWIF/HIDEIF empty fields ( Gary Krockover 2005)
  20. Re: SHOWIF/HIDEIF empty fields ( Stuart Tremain 2005)
  21. Re: SHOWIF/HIDEIF empty fields ( Kenneth Grome 2005)
  22. Re: SHOWIF/HIDEIF empty fields ( Donovan Brooke 2005)
  23. Re: SHOWIF/HIDEIF empty fields ( Kenneth Grome 2005)
  24. Re: SHOWIF/HIDEIF empty fields ( Frank Nordberg 2005)
  25. Re: SHOWIF/HIDEIF empty fields ( Kenneth Grome 2005)
  26. SHOWIF/HIDEIF empty fields ( Frank Nordberg 2005)
Gary Krockover wrote: > > Correct, my mistake - it's not the landing page on forms but when > recalling a pre-populated form, such as in the case where the visitor > missed a required field and I've redirected them back to the form while > checking for existing values in a custom "required fields" situation. > > Example, visitor fills in form, that appends to a db but they missed a > field. I redirect them back to the form and repopulate the form from > what they did fill in. .... > but I'm still checking to see if it > equals [raw][field][/raw], either there or when repopulating the form. It should, but remember to put the comparasion string in the right order: [SHOWIF/HIDEIF [raw][FIELD][/RAW]=[FIELD]] or possibly: [SHOWIF/HIDEIF [raw][FIELD][/RAW]=[url][FIELD][/URL]] You really ought to do a double check with both that one and [SHOWIF/HIDEIF ![url][FIELD][/URL]] An unfilled form field should be passed on as a blank rather tha remain undefined although that doesn't always happen. Another method is to have each field prefilled in with a dummy value: and then check for that value. Not foolproof unfortunately Or you can do it the old fashioned way with JavaScript of course. If you want absolute max safety, you can easily combine all of those methods. Then only the absolute best of fools can manage to mess it up. Frank Nordberg http://www.musicaviva.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://webdna.smithmicro.com/ Frank Nordberg

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:

Simple way to create unique SKU (1997) The Best Shopping Cart Solution I Have Come Upon (2003) WC1.6 to WC2 date formatting (1997) Request for page test (2003) Release of 2.01? (1997) PSC recommends what date format yr 2000??? (1997) Shhh... (2006) Adding Message to Order (1997) partial credits (2003) Javascript/WebCatalog form population (2001) Problems with [Applescript] (1997) Summing fields (1997) [sendmail] questions... (1997) New index for docs (1997) Wait, I forgot something! (was authenticating a seconduser, the sequel) (1997) pop up building with summarize (1998) Searching on 3 different fields *CORRECTION* (2003) ShowNext (1997) WebCat B13 Mac CGI -- Frames question (1997) still facing truncated [texta] problem (2000)