Re: Displaying text and populating form fields
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 61205
interpreted = N
texte = Hello,I have a form where user fill out a text area, then when they post the page, the resulting page sends an email with the content of their message. I also display their message on the webpage. The data is never stored in a database. When I display the data on the results page, all line breaks are lost .. What should I be doing to this data so that the line breaks are preserved on this results page?on the message page, the textarea is:
On the results page, to display their message from the textarea on the preceeding page:[unurl][message][/unurl]Over time I have tried many things, but the above has been the best so far. I would really like to be able to display the line breaks in their message without having to store it in a database.ThanksOn Thu, 24 Feb 2005 13:30:15 +0800  Kenneth Grome 
 wrote:> >on 2/23/2005 1:30 pm, Donovan Brooke at dbrooke@euca.us so noted...> >> >>  as well as it doesn't protect against when someone goes to edit > >>formerlly> >>  textarea input (input with carraige returns) in a hidden form > >>field.> >> >As an aside, I've a CMS that's been used for the last five years > >with a> >variety of Mac and PC users on various browsers. It passes > >textarea-entered> >data with plain, unescaped, drop-to-the-next-line line breaks using > >hidden> >form fields across multiple pages without any problems.> > > That's because the data is initially entered by the visitor into a > textarea field which can pass line break characters, and you're > continuing to pass the data via hidden form fields which can *also* > pass line break characters.> > If you switched from hidden fields to text fields when passing your > data you would immediately learn that everything after the first > line break character will be lost, because text fields cannot pass > line break characters or anything that follows a line break > character.  Of course you're not going to do this, I'm only saying > this to illustrate a point, and my point is this:> > Hidden fields and textarea fields work exactly the same, except that > one is editable by the visitor and one is not.  It's the text fields > that cannot pass line break characters, and this is what creates the > problem ...> > -- > > 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:
Hello,I have a form where user fill out a text area, then when they post the page, the resulting page sends an email with the content of their message. I also display their message on the webpage. The data is never stored in a database. When I display the data on the results page, all line breaks are lost .. What should I be doing to this data so that the line breaks are preserved on this results page?on the message page, the textarea is:On the results page, to display their message from the textarea on the preceeding page:[unurl][message][/unurl]Over time I have tried many things, but the above has been the best so far. I would really like to be able to display the line breaks in their message without having to store it in a database.ThanksOn Thu, 24 Feb 2005 13:30:15 +0800  Kenneth Grome  wrote:> >on 2/23/2005 1:30 pm, Donovan Brooke at dbrooke@euca.us so noted...> >> >>  as well as it doesn't protect against when someone goes to edit > >>formerlly> >>  textarea input (input with carraige returns) in a hidden form > >>field.> >> >As an aside, I've a CMS that's been used for the last five years > >with a> >variety of Mac and PC users on various browsers. It passes > >textarea-entered> >data with plain, unescaped, drop-to-the-next-line line breaks using > >hidden> >form fields across multiple pages without any problems.> > > That's because the data is initially entered by the visitor into a > textarea field which can pass line break characters, and you're > continuing to pass the data via hidden form fields which can *also* > pass line break characters.> > If you switched from hidden fields to text fields when passing your > data you would immediately learn that everything after the first > line break character will be lost, because text fields cannot pass > line break characters or anything that follows a line break > character.  Of course you're not going to do this, I'm only saying > this to illustrate a point, and my point is this:> > Hidden fields and textarea fields work exactly the same, except that > one is editable by the visitor and one is not.  It's the text fields > that cannot pass line break characters, and this is what creates the > problem ...> > -- > > 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/
 "eLists" 
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:
 
emailer w/F2 (1997)
 
Truncated [textA] (2000)
 
California Tax Rates (1998)
 
Displaying photo attached to first record (1997)
 
Re:Can anyone help me with this shipping thing? (1998)
 
Spiders (1998)
 
[WebDNA] EMailFolder/ (2016)
 
Limit on nested [ShowIf]'s? (1997)
 
Javascript and Search Results (1998)
 
What file? (1997)
 
Emailer not working (1998)
 
Resolving variables into field names (1998)
 
New WebDNA Solutions ... (1997)
 
Logging purchases (1997)
 
Digest Version (2000)
 
Review comparison by PC Magazine: Open for On-line Business (1997)
 
Help!  WebCatalog not writing dbs to disk (2001)
 
Database formats (2003)
 
chat opinion ... (2002)
 
 mySQL numfound (2006)