This is because the sub TAF (TAF Call in an @INCLUDE) reference is not processed as a TAF by the server. It is just passed through as XML inside. The original @INCLUDE
Ben Johansen - http://www.pcforge.com Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm Latest downloads & List Archives @ http://www.witango.ws -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Wilcox, Jamileh Sent: Tuesday, November 26, 2002 3:04 PM To: Multiple recipients of list witango-talk Subject: Witango-Talk: <@INCLUDE> problem Is there a problem with using <@INCLUDE> with a TAF file? Or a problem with nesting <@INCLUDE> in an inline frame? If so, is there another method to use? I've got an entry page that uses an IFrame with a taf src file. That src file has an <@INCLUDE> for another taf file. The browser shows the structure of the final taf file (i.e., the If/Else statements, the Search statements, etc) rather than the correct output. There's also a couple of extra brackets thrown in for good measure (like so): ]]> I've searched all 3 tafs for open brackets, open tags, etc., without any luck, both looking through the tafs & using the View Source. I've stripped all 3 tafs down to essentials (just HTML, HEAD, BODY, etc.) and still have the same problem (which seems to eliminate the open tags possibility). I've created new copies of all 3 tafs. Nothing seems to fix this, so I'm starting to wonder if I'm doing something that Witango just won't do. Any suggestions? Thanks! jamileh ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
