Hmm... this is kind of interesting.
So, if you want to kill it at its source, you're going to have to modify <sugar_root>/data/SugarBean.php. On line 2052 you'll find the function you're looking for: PHP Code:
function preprocess_fields_on_save()
{
$GLOBALS['log']->deprecated('SugarBean.php: preprocess_fields_on_save() is deprecated');
}
The interesting thing is that this function is doing nothing. Its already completely deprecated, so idk why Sugar is still calling it. Maybe someone didn't call housekeeping? Anyway, if you just comment out the log call in this function it will/should stop logging it.
I say will/should because I haven't done it; I'm very weary of making any changes to core sugar files. SugarBean.php is the core of cores - its like the Java Object class of SugarCRM. That being said, if your other, more important log calls are of type 'error' or higher, rather than changing this you should go to Admin->System Settings, scroll down to Logger settings and switch your logging level to 'error' or higher. If they're on a lower level, then if you make this change to SugarBean.php remember that it isn't upgrade safe so you may have to make it again every time you upgrade until they stop calling the function.
*edit*
I totally forgot about the second deprecated call. its coming from line 2174 in the same file. Looks like this: PHP Code:
if ( $reformatted ) {
$GLOBALS['log']->deprecated('Formatting correction: '.$this->module_dir.'->'.$field.' had formatting automatically corrected. This will be removed in the future, please upgrade your external code');
}
Do the same thing, comment out the log call, to get rid of it if you decide not to change your logger settings.
Bookmarks