Re: Displaying text and populating form fields
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 61179
interpreted = N
texte = >Kenneth Grome wrote: >>>... 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 ... > > >Yea Ken, I corrected that post with my post right after it. > >Donovan Sorry I guess I missed the correction, there were lots of posts in this thread but only a couple that contributed to defining a clear set of guidelines, which is actually what I was after. Thanks for being one who added something useful to the discussion! -- 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:
>Kenneth Grome wrote: >>>... 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 ... > > >Yea Ken, I corrected that post with my post right after it. > >Donovan Sorry I guess I missed the correction, there were lots of posts in this thread but only a couple that contributed to defining a clear set of guidelines, which is actually what I was after. Thanks for being one who added something useful to the discussion! -- 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:
Robert Minor duplicate mail (1997)
OK, here goes... (1997)
Webdna is dead! (2003)
Software & Sites (1998)
[Reload mydata.db] (1998)
Multiple catalog databases and showcart (1997)
Re1000002: Setting up shop (1997)
WebCommerce: Folder organization ? (1997)
Formatting a .txt file (1998)
RequiredFields and MacOS X Server? (2000)
WebCat Emailer & Liststar (1997)
Grep on Emails w/ Multiple Dots (2004)
-tmp (2000)
This list needs a digest: rant, rave... (1997)
Limiting user access to .tmpl files (1997)
passing search criteria (1997)
Unzip (2005)
Various Problems (1997)
CMSBuilder (2004)
[WebDNA] Archives (2009)