Here's a long standing problem: the 404 error page for witango. If a client
hits a nonexistent .tml or .taf URL, they get a witango-generated error.
inelegant. One should be able to customize that to the 404 error page of your
choice. Bill Conlon suggested the logic, which makes perfect sense.
We have been using a custom error file on our witango server for years. It has
quite a bit of code/meta tags in it. Witango 5.5 on windows.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
15520 Coutelenc Rd
Magalia, Ca 95954
ph: 530.645.4040 x222 fax:
Added to the list.
I agree that there should be separate error files for certain groups of errors:
No TAF/TML file found (aka 404)
Witango Execution Can't continue (error in TAF/TML/TCF)
Configuration/Server issue (aka 5xx)
I also don't like that the hitting the queryTimeout can't be processed
what I don't get is that there is an architecture for handling errors in a
custom fashion by pointing to an error file. A placeholder file is installed by
default. Just if you put anything in that file, the server crashes. Is that a
bug in the server, or was Bill Conlon's code somehow a wrong
Roland,
On the 5.5.020 and 6.0.3 Witango (Windows platform) putting code in that file
works as expected. I believe you are familiar with error handler, which parses
the error, creates objects and called methods, executes database actions, sends
email and returns various friendly results to the
I'm running 5.0 on both servers. Is that a known bug for 5.0?
On Dec 14, 2010, at 1:58 PM, Robert Shubert wrote:
Roland,
On the 5.5.020 and 6.0.3 Witango (Windows platform) putting code in that file
works as expected. I believe you are familiar with error handler, which
parses the error,
This feature should work properly, especially in the latest build (5.0.1.065).
It is possible that the contents of error.tml could be such that the server may
crash, but I have no knowledge of this case. You may want to try simplifying
the file.
Robert
-Original Message-
From: Roland
