Update! So far I have come up with this code mod to simulate a WYSIWYG but, I would rather know how to pipe through the same stream of code that add.cgi really does to write to record to validate.db (it puts the `` inplace of \n, etc.) and the stream of nph-build.cgi does (in db_utils.pl to change it back to \n or what ever). This would be more of a cleaner way of doing this so that one does not have to maintain different areas of the code.
________________ code is:
sub site_html_add_confirm {
# -------------ADDED THIS ROUTINE 7/99 FOR SUCCESS-------------------------------------------
# This routine determines how the add success page will look like.
&html_print_headers;
#Start of -Try this to make deail wsiwsg
#site_html_detailed
if ($in{'Details'} !~ /<([p|P]|(br|BR))>/)
{
#$in{'Details'} =~ s/\r\r/<p>/g;
#$in{'Details'} =~ s/\r\n/<p>/g;
$in{'Details'} =~ s/\n/<br>/g;
}
##END of -Try this to make deail wsiwsg
print &load_template ('add_confirm.html', {
# print &load_template ('detailed.html', {
%in,
%globals
});
}
The # are just where I was debuging.
To have better control over submits is important because I have found some characters used in html will mess up the links.db and validate.db to a point that will cause a corrupted file(s). Thereby messing up ID's , etc. in the begining of the records (to name a few).
I like the idea here... the WYSIWYG (what you see is what you get) add-confirm step/mod is great to help keep things straight.
Thanks t_dog for putting me on this track. ( http://www.gossamer-threads.com/scripts/resources/Detailed/173.html ). It is not totally what I need but it is a great (95%) start on the right direction on what we need.
TimRyan
[This message has been edited by timryan (edited July 30, 1999).]