force_error_page when used causes headers to be sent and can cause header already sent. i.e. when i disable $VAR['page_no'] global variable for an example
perhaps the error handling might be better changes to SQL error handling because i think all errors that are handled via this method are SQL
Definately do not delete my custom error handling subsystem as it is very useful for finding errors.
currently when a SQL statement fails I get my custom error page shoing me what function location etc.. But if I enable
in adodb.php all adodb/mysql errors are handled by Whoops. This is not a bad thing but is not as quick to diagnose.
These might be useful for later development
force_error_page when used causes headers to be sent and can cause header already sent. i.e. when i disable $VAR['page_no'] global variable for an example
perhaps the error handling might be better changes to SQL error handling because i think all errors that are handled via this method are SQL
Definately do not delete my custom error handling subsystem as it is very useful for finding errors.