ok, thanks a bunch (: ----- Original Message ----- From: "John McGowan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 09, 2003 9:55 AM Subject: Re: Witango-Talk: help getting T2K programs running in new Witango v5 AS
> Atrix, > > You definitly still need the @clearerrors. My workaround is to be used > along with the @clearerrors tag. > > You might be able to put it right there in the error html, but I'm not > sure when With actually changes the http header to 500. The reason I > put it at the bottom of my page delivery engine is because I use the > clearerrors in several places, and didn't want to have to put the > workaround in all of those places. Putting it at the bottom works in my > situation. > > /John > > Atrix Wolfe wrote: > > >Hi John, > > > >do you do this along with the <@clearerrors> or is it in place of? > > > >----- Original Message ----- > >From: "John McGowan" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Wednesday, July 09, 2003 9:35 AM > >Subject: Re: Witango-Talk: help getting T2K programs running in new Witango > >v5 AS > > > > > > > > > >>The problem could be that you are encountering an error, and in the > >>error html using the @clearerrors tag. > >> > >>Witango broke the @clearerrors tag when they added the functionality to > >>change the HTTP header that Scott is talking about below. Because using > >>the @clearerrors tag should clear the error and continue processing with > >>no problems. However, Witango forgets to set the HTTP Status code back > >>to "200 OK" when you use @clearerrors. > >> > >>I raised this as a bug with Witango a couple weeks ago. > >> > >>Until the bug gets fixed, i'm using the following work around. > >> > >><@if expr="<@LOCATE STR=<@Version> FINDSTR='5.0.1'> > 0"> > >><@ASSIGN local$httpHeader "HTTP/1.1 200 OK<@CRLF>Content-Type: > >>text/html<@CRLF><@SETCOOKIES><@USERREFERENCECOOKIE><@CRLF><@CRLF>"> > >></@if> > >> > >>pseudocode reads.. > >> > >>If this is Witango > >> Set the HTTP Header back to 200 OK so that the page isn't reported as > >>an error. > >> > >>You could put this chunk of code in the footer of your pages as long as > >>it's before any content has been sent back to the browser (before any > >>pushed actions) > >> > >>/John > >> > >> > >>Scott Cadillac wrote: > >> > >> > >> > >>>Hi Trevor and Giorgio, > >>> > >>>With Witango v5, when errors occur, Witango is now properly assigning the > >>>HTTP header status code (typically 500). > >>> > >>>This causes MS Internet Explorer and other browsers to display a > >>> > >>> > >"generic" > > > > > >>>error page. > >>> > >>>Try turning off or on the "Show friendly HTTP error messages" in MSIE. > >>> > >>>>From the MSIE main pull-down, click "Tools", then "Internet Options...", > >>>then click on the "Advanced" tab, and toggle the check-mark for "Show > >>>friendly HTTP error messages" - click "OK" to save your changes. > >>> > >>>This should allow you to see more information about the problem. > >>> > >>>Hope this helps. Cheers.... > >>> > >>>Scott Cadillac, > >>>Witango.org - http://witango.org > >>>403-281-6090 - [EMAIL PROTECTED] > >>>-- > >>>Information for the Witango Developer Community > >>>--------------------- > >>> > >>>XML-Extranet - http://xml-extra.net > >>>403-281-6090 - [EMAIL PROTECTED] > >>>-- > >>>Well-formed Development (for hire) > >>>--------------------- > >>> > >>>-----Original Message----- > >>>From: Ferr� A&T - Giorgio Tassistro [mailto:[EMAIL PROTECTED] > >>>Sent: Wednesday, July 09, 2003 9:41 AM > >>>To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > >>>Subject: Fw: Witango-Talk: help getting T2K programs running in new > >>> > >>> > >Witango > > > > > >>>v5 AS > >>> > >>> > >>>Trevor, > >>> > >>>I discover that If you put before the action a empty "results page" with > >>>push, the TAF go ! > >>>Check this out! > >>> > >>>Giorgio > >>> > >>>----- Original Message ----- > >>>From: Ferr� A&T - Giorgio Tassistro > >>>To: [EMAIL PROTECTED] > >>>Sent: Wednesday, July 09, 2003 5:02 PM > >>>Subject: Re: Witango-Talk: help getting T2K programs running in new > >>> > >>> > >Witango > > > > > >>>v5 AS > >>> > >>> > >>>Trevor, > >>> > >>>I have just now, send the same problem to Witango. > >>>The problem (I think) is that Witango 5 does't know corretly the ODBC > >>> > >>> > >error > > > > > >>>( only on Pervasive.SQL ?) . > >>>If you use "Error HTML page", it does't go, sure. > >>>I wait some solutions. > >>> > >>>Regards > >>> > >>>Giorgio Tassistro > >>>----- Original Message ----- > >>>From: Trevor Green > >>>To: Multiple recipients of list witango-talk > >>>Sent: Wednesday, July 09, 2003 4:53 PM > >>>Subject: Witango-Talk: help getting T2K programs running in new Witango > >>> > >>> > >v5 > > > > > >>>AS > >>> > >>> > >>>Platform is Win2K Server, Witango v5.0 (latest production build). > >>> > >>>Programs have not been opened by T2K Development studio and/or converted > >>>(i.e. are straight from T2K server). Programs execute correctly the > >>> > >>> > >first > > > > > >>>time they are run. However, when I open a .taf containing a form that > >>> > >>> > >when > > > > > >>>submitted calls the .taf with different arguments I get an HTTP 500 > >>> > >>> > >Internal > > > > > >>>server error. > >>> > >>>Can anyone steer me in the right direction to try and troubleshoot? > >>> > >>>Many thanks > >>> > >>>Trevor Green > >>> > >>>________________________________________________________________________ > >>>TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > >>> > >>>________________________________________________________________________ > >>>TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > >>> > >>>________________________________________________________________________ > >>>TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > >>> > >>> > >>> > >>> > >>> > >>________________________________________________________________________ > >>TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > >> > >> > >> > > > >________________________________________________________________________ > >TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > > > > > > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
