Hello all -
Odd question, but I've got a PLP set for the creation of events here at
the school, and three of the input fields are textareas. Normally, to
insure that they display correctly, I use the following to replace
newlines with <BR> tags:
<!--- BRCRLF represents a single carriage return --->
<CFSET BRCRLF="#Chr(13)##Chr(10)#">
<CFSET Form.Location=REReplace(Form.Location, #BRCRLF#, "<br>", "ALL")>
<CFSET Form.Location=NewLocation>
or I can use a similar block of code in the display handler to do it on
the fly.
However, when I try it on the events which have been run through the
PLP, it doesn't work on the fly. It will work if I place the code on the
page which submits the particular textarea, but not if I place the code
at the end of the PLP (for post processing, for example, once all fields
are filled out). The problem is that if I put this code in the page
itself, then if the user goes 'back' to it, it has HTML codes in it &
the unsophisticated user may get confused.
I can get around this by converting BACK to CHR(13)CHR(10) if I have to,
but I'm curious to know why this isn't working. I have to figure that
the ParagraphFormat() function does something similar to searching for
CHR(13)CHR(10)CHR(13)CHR(10) and replacing them with <P> tags, but
perhaps not.
In any case, these fields seem to me to have no newline codes in them;
is there some other indicator of a newline & paragraph I can search on?
Any reason why these codes should not be there?
Thanks in advance for any information.
--
Peter Ivanick
Web Developer, School of Veterinary Medicine
University of Pennsylvania
[EMAIL PROTECTED]
http://www.vet.upenn.edu/
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
