This behavior was implemented intentionally, so that tersus.log is dedicated to unhandled errors (exceptions).
Currently, we recommend you handle errors caught via an error exit in a separate (modeled) logging mechanism, writing the contents of the Error structure to some database table - you can use the Log module (from the modules section of the palette), as a basis for this.
I did add feature request #312, though I don't expect implementing this in the near future.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
