Apr 29th, 2009, 11:26 AM
Quote:At that moment a php error message comes in instead of a humanly readable one...
Blurgh! That shouldn't happen.
Check your error_reporting levels. If you're using the API, it'll be using the default error reporting level found in library.php ($g_default_error_reporting = 2047). You'll want to lower that value to 1 to only display true errors. Just add that line to your config.php file (also found in your /global folder) with the value of 1.
Are you using the API, btw? Or just posting it to process.php?
If that's the source of the problem, changing that value should at least hide the error. But now we need to capture it... and there I'm drawing a blank.
When a submission goes through there are a LOT of things going on, many of which can go wrong. Unless the problem is a show stopper (can't find the form, DB down etc), Form Tools blithely bypasses the minor problems and puts through the submission. Right now, there's no way to capture these errors.
Give me a few more details about your case (including the error message that you're seeing) and I'll see if I can come up with a solution!
- Ben