My new blog

My name is Ken Brill.  I live in central Missouri about 100 miles south of St. Louis. My wife and I run a small 30-acre hobby farm here in Missouri, and I work as a developer from a small, dark corner in my basement.  Out here we only have satellite Internet (Viasat) so that's fun.  They advertise 25Mbs but I rarely see anything better than 12Mbs.  It does the job but I miss my cable modem sometimes.

On the farm, we raise about a dozen goats and sheep, 2 cows, 3 horses, 7 dogs (ranging from a Chihuahua and Maltese to a pair of Great Pyrenees, 6 cats of no discernible use, 4 kids (all girls), and a few dozen Chickens, Guinea fowl, Peacocks, Turkeys, and Ducks.  We have been at it for 5 years now so we are still learning but it's a lot of fun when it's not freezing outside.

The last 12 years I have specialized in SugarCRM.  I began with version 2.5 when a small company I worked for started using it and I have been working on SugarCRM ever since.  I had my own consulting company for a few years where I sold a product called 'Sugar Fully Loaded' that was essentially the SugarCRM CE product with several popular add-ons already loaded and merged (no such thing as upgrade-safe back then).  I spent 9 years after that working at SugarCRM in different roles and now I work remotely as a senior developer on an enterprise level installation and we are getting ready to roll out version 7.10 next year.

Adding Audit Logs to Reports

My users had a need to query the audit log for various modules in ways that the current built in system would not allow.  Now I could create advanced report after advanced report but really I hate making advanced reports. So I added myself a JIRA task to create some way of reporting on the Audit Logs.

All the files are available for download from the GitHUB link at the end of this post.

This was my list of criteria for this project

1. I need a way to report on any modules audit log
2. I need a way that allows a manager to create their own reports
3. That method has to be familiar to them already (this was really me saying I wanted it in the Reports module)
4. It must not allow editing of Audit Logs in any way
5. It must be fast over millions of records (some of our audit logs are huge)
6. It must translate all the raw data back into English
7. It must allow our system admins to include that new audit_events table data in the reports
8. It cant break the current Audit code

Overriding MysqliManager.php

Overriding the stock SQL Managers

It took me a while to figure out how to override the core MysqliManager class so that I could add some code to email me the SQL errors that usually just go to my logs.  At first I tried just creating the custom file, expecting it to be read like others I had created, but I found that you actually  have to tell the system to use your custom class in the config_override.php file like this