|
Tony, LAS does trap some internal error messages so that it can spit out user friendly error messages. For all the rest, however, we've left the programmer friendly debugging information. We agree that this is not very helpful for the end user and perhaps may frighten some of them away. You can modify the way that errors are handled in LAS by modifying the code in las/server/LAS/Server.pm. If you search for 'sub handle_errors' you will find a BEGIN block that takes an error message, checks to see if it recognizes any strings in that message and sends the user an appropriate response. If no recognized strings are found, the error message is returned with the LAS transcript appended. It should be straightforward for you to modify this block of code so that you send back a standard response by default. You could also modify the LAS::Server::Error package in this module so that the LAS transcript is not appended. This would greatly simplify the output. Although these are straightforward changes, you should save the changes you make to a backup file. The Server.pm file is part of the 'core' LAS code and we don't expect you to modify it. If you use CVS to update your LAS installation, this file, and your changes, will be overwritten. Let me know if you need some more guidance in making the changes you want. -- Jon Tony Jolibois wrote:
|