SugarCRM and Saleslogix for Atlanta, GA and Mobile, AL

SugarCRM 6.3 introduces a neat new feature of Sugar Logic, the field-calculating excel-style syntax’d scripting language available inside of Studio. The new rollup feature allows a certain field to gather information from specific fields in related modules. The values can be counted, averaged, summed or Read More »

While upgrading an older SugarCRM System from 5.2.0 to 5.5.1, I encountered errors regarding a missing method getloggerrepository(). Searching the SugarCRM forums I quickly found a resolution by modifying some core logger-related files. The fix was simple enough, commenting out a few lines. Follow the instructions provided by SugarCRM Forum Member westphal here in his thread resolved: undefined LoggerManager::getloggerrepository().

I resolved the issue by commenting the following 5 lines in include/logging.php:

if (! isset($simple_log) || $simple_log == false) {
$config = new LoggerPropertyConfigurator();
$config->configure('log4php.properties');
}

From what I can tell, the issue is partly SugarCRM bug in 5.2.0 and/or 5.5.1, and also caused by the outdated version of the Zucker Reports module installed on the system. westphal noted his system had ZuckerReports as well as other modules that used similar methods for interacting with the SugarCRM Logging tools.

It’s worth noting that attempting to simply uninstall Zucker won’t solve the problem, because Module Loader will fail due to the same Logger references that trip up Repair & Rebuild.

After applying westphal’s fix, removing Zucker, and a Repair & Rebuild, the system was stable at 5.5.1 and I was able to continue my upgrade.

SugarCRM Logic Hooks are a powerful way of interacting with data or other systems on specific system actions, usually retrieving or saving a record. A common customization challenge we face is saving a record and performing an action if a particular field has changed. For example, if a phone number field changes for a contact, we want to merge the updated contact record with another system via an API. Let’s look at how to detect changes. Read More »

For our ongoing projects, sometimes we need to upload customizations to key files that don’t necessarily invoice creating new modules or fields. They’re just code changes. I’ve been using and re-using this manifest.php for such situations for a few months now and it seems to work nicely.

When I need it, I copy the file from an old module and paste it into my current directory. Read More »

SugarCRM’s Studio tool is great for administrators to point-and-click their way into field creation, but there are alternative methods. Creating fields in code has the advantage of gaining 100% control of the field, which can be especially helpful if you desired, for instance, multiple Flex Relate fields. You also gain the ability to keep the field under version control. Read More »