I too have encountered this effect. It seems as though the action has
accumulated the text in the results, no results AND error pages and
then it flows it to the output.
I have had to put all the HTML page info into separate results pages
that are under IF/ELSEIF/ELSE actions that are based on variables
within the results, no results and error pages. I also make sure to
add a <@purgeresults> tag at the top of those pages. The
<@purgeresults> tag does not work in the action.
I struggled with this for a long time when implementing a failsafe
mode in my web applications when tied to yoyo databases.
So the long and short of it is YES you have to move the HTML content
into logic outside of the action. Perhaps this will be fixed in the
new version.
On 5/14/2002 at 11:45 AM -0700, this was written:
>I have used <@CLEARERRORS> in a error results so that I can continue
>to process my Tango application, but it seems that Tango contines to
>read the Results and No Results pages in the same action. It
>however seems to process them as text, so the tags in those pages
>appear as text a the top of my web page. Is there a way around this
>that doesn't involve moving the results/no results attributes?
>
>Shannon Henderson
>Web and System Services
>Reed College
>Portland, OR
--
Tom
Voice: 416 760 0268
Fax: 416 760 7263
E-mail: [EMAIL PROTECTED]
Web Site: www.aboutcomputers.com
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
