Author Topic: thanks for the new-improved backtrace! (Read 527 times)

ken · October 17, 2012, 06:21:16 pm

Folks,

Just a generic thank-you for improving the backtrace information. Very helpful!

Ken

totten · October 19, 2012, 10:13:20 am

Probably a consequence of http://issues.civicrm.org/jira/browse/CRM-10724

On a related note, there's still room for improvement. With my D7+CiviCRM setup, PHP parse errors appear badly formatted (the output is plain-text but the browser thinks it's HTML), and unhandled exceptions bubble up to Drupal (which never displays the full backtrace). For the AJAX-driven queue, we have CRM_Queue_ErrorPolicy which is more aggressive about catching these and reporting them in a normalized format. It would be nice to adapt the technique to CRM_Core_Invoke so that parse-errors and unhandled exceptions use our normal error UI.

ken · October 20, 2012, 11:56:57 pm

I don't really want a "thank you" post to become a "please" post, but it would be nice to have the backtrace include ...

The invoked URL to assist with reproducing the error
The identity of the CMS User (if any) to assist with tracking down the context, and also to provide training
Most (all?) DAO/BAO objects have an "id" field. Displaying that would help when tracking down the conditions when errors occur

CiviCRM Community Forums (archive)

News:

Author Topic: thanks for the new-improved backtrace! (Read 527 times)

ken

thanks for the new-improved backtrace!

totten

Re: thanks for the new-improved backtrace!

ken

Re: thanks for the new-improved backtrace!