Re: Displaying text and populating form fields

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 61177
interpreted = N
texte = >... it doesn't protect against when someone goes to edit formerlly textarea >input (input with carraige returns) in a hidden form field. Sorry but you lost me here. I cannot imagine any time when will a visitor try to edit data that's contained in a hidden field. They don't even know about hidden fields so of course they won't be editing values in those fields. Are you perhaps talking about using a text field to edit data that was originally entered via textarea? If so, you will lose any line break characters because text fields cannot contain line break characters. This really should be considered a programming error, not a limitation of webdna. If you use the wrong field type you're bound to create problems ... -- Sincerely, Kenneth Grome www.kengrome.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: Displaying text and populating form fields (again) ( Kenneth Grome 2005)
  2. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  3. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  4. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  5. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  6. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  7. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  8. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  9. Displaying text and populating form fields (again) ( eLists 2005)
  10. Re: Displaying text and populating form fields (again) ( "eLists" 2005)
  11. Re: Displaying text and populating form fields ( eLists 2005)
  12. Re: Displaying text and populating form fields ( "eLists" 2005)
  13. Re: Displaying text and populating form fields ( John Peacock 2005)
  14. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  15. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  16. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  17. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  18. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  19. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  20. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  21. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  22. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  23. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  24. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  25. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  26. Re: Displaying text and populating form fields ( Terry Wilson 2005)
  27. Re: Displaying text and populating form fields ( John Peacock 2005)
  28. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  29. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  30. Re: Displaying text and populating form fields ( Terry Wilson 2005)
  31. Displaying text and populating form fields ... ( Kenneth Grome 2005)
>... it doesn't protect against when someone goes to edit formerlly textarea >input (input with carraige returns) in a hidden form field. Sorry but you lost me here. I cannot imagine any time when will a visitor try to edit data that's contained in a hidden field. They don't even know about hidden fields so of course they won't be editing values in those fields. Are you perhaps talking about using a text field to edit data that was originally entered via textarea? If so, you will lose any line break characters because text fields cannot contain line break characters. This really should be considered a programming error, not a limitation of webdna. If you use the wrong field type you're bound to create problems ... -- Sincerely, Kenneth Grome www.kengrome.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/ Kenneth Grome

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:

Variable prices and Formulas.db (1997) Another question (1997) Using Applescript to process WebCatalog functions (1998) emailer error -108 (1997) UPDATE PROBLEM (1997) Redirect frame targets (1998) dates and hex formatting (1997) What folder??? (1999) Announce: WebMerchant 3.0 for Mac shipping now (1998) Date stamp and purging (1998) OT: 800x600 (2003) Building Calendars (1997) Webcat Hosting in London or UK (2003) Emailer update for Mac? (1998) WebCat2.0 [format thousands .0f] no go (1997) Help! WebCat2 bug (Ben's input) (1997) item sorting (1997) trouble updating records in database (1998) Unexpected error (1997) WebCatalog 2.1 for NT (1998)