MySQL error 1054: Unknown column 'config.deleted' in 'where clause'

pgr · 29 September 2022 11:28

I’m sure it’s possible to get them, I’m not sure why you’re not seeing it, maybe there is some other way.

So many problems would be solved in a much quicker and easier way if this PR I made more than two years ago had been merged… sigh…

github.com/salesagility/SuiteCRM

Improved logging, richer stack traces

salesagility:hotfix-7.10.x ← pgorod:ImprovedLogging7.10

opened 10:40AM - 02 Apr 20 UTC

pgorod

+411 -51

## Description, Motivation and Context Adds some `config_override.php` options …to get more information in the logs, specifically: - ability to ask for richer information regarding a single error message, making it easier to focus on a specific problem - ability to get more highly technical information without being a technical user (useful for Forums troubleshooting and gathering info from clients) - get IDE-level stack traces, with both argument names **and values** ## Documentation preview https://pedro--suitedocs.netlify.app/developer/logging/#_advanced_logging_configuration ## How To Test This Please read the documentation linked above, there are many options. An important part of the testing is confirming that **nothing changes** until we start putting options in `config_override.php`. This will make me more confident about putting the code out there :-) For a simple run, you can test this by adding entries in your `config_override.php` such as these (all explained in the Docs page): ```php $sugar_config['show_log_trace'] = 'One2MBeanRelationship'; // use a boolean true for all; or a string as filter $sugar_config['show_log_trace_with_eol'] = true; $sugar_config['show_log_trace_overview'] = true; $sugar_config['show_log_trace_trim'] = 500; $sugar_config['show_log_trace_source'] = 1; ``` ## Answers to some valid concerns 1. This is **backwards compatible** because it does not assume any config values to be there, always uses sensible defaults, and respects the previous meaning of `$sugar_config['show_log_trace']`. 1. This code is complex, and some bug can have slipped by, but **it only runs in the cases where you select log traces**, so it's easy to turn off, and shouldn't affect production systems. 1. Some of this code impacts **performance** (lots of string operations, more file activity) but it's always opt-in: the impact only occurs when you configure it to happen. 1. This is accompanied with a **warning** in Documentation: using log traces with argument values might leave sensitive information in the system logs. Use it only temporarily for troubleshooting purposes; obfuscate the information before posting it online; double-check that your logs are only accessible to admins; delete the logs when finished troubleshooting. ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ### Final checklist - [X] My code follows the code style of this project found [here](https://docs.suitecrm.com/community/contributing-code/coding-standards/). - [X] My change requires a change to the documentation. - [X] I have read the [**How to Contribute**](https://docs.suitecrm.com/community/contributing-code/) guidelines.