[Solved] Debugging options are independent

[John.K]

The 'Debugging and Error Handling' settings page has the 'Enable debugging', 'Enable Drupal Watchdog Logging' and 'Enable backtrace' options.

These can be enabled independently, ie: debugging can be disabled, but backtrace can be enabled.

The documentation (http://wiki.civicrm.org/confluence/display/CRMDOC/Debugging+for+developers) suggested that you must enable debugging to access the backtrace. I am just about to update the documentation to say they are independent.

The UI in CiviCRM says 'Set this value to Yes if you want CiviCRM error/debugging messages to also appear in Drupal error logs'.

I am about to put up an issue with a PR to remove the 'also', since this could imply that it depends on whether or not debugging is enabled.

I suppose this opens up the question about whether all these settings should be independent of each other? It makes sense that we can log errors to watchdog without having to enable debugging; so the PR also moves the Drupal debugging option to the top of the list. This keeps the two 'non-production' options together, so that the backtrace could be more easily made 'dependent' on debugging being enabled; if people feel that should be the case.

IMHO it should be fine to keep them independent, as long as the help text and documentation makes this clear.

[John.K]

Issue: https://issues.civicrm.org/jira/browse/CRM-15985
PR: https://github.com/civicrm/civicrm-core/pull/5190

[John.K]

PR merged, many thanks. Documentation page also updated.