ELASTICSEARCH: Restarting Elastic Search SugarCRM Installation

Error:
Unable to connect to Full Text Search server, please verify settings

Solution:
1. Check ElasticSearch is running
   >  sudo /etc/init.d/elasticsearch status
2. If status is not running, restart
   >  sudo /etc/init.d/elasticsearch restart
3. If the above does not work, modify /etc/elasticsearch/elasticsearch.yml as follows:
discovery.zen.ping.multicast.enabled: false and repeat 1 & 2

SUGARCRM: Debugging SugarCRM 7.x

Inside a Logic Hook or any other backend file:

echo "<pre> DEBUGGING: ".PRINT_R('BEFORE' ,TRUE)."</pre>";

NOTE: The above command is for debugging purposes only. Make sure to remove that command before pushing to either production or QA.

UNIX: Checking Logs in Real-Time

$>> tail -f <filename>

SUGARCRM: 500 Error when using $GLOBAL['log']->fatal()

Error: HTTP Error: 500 when saving a record.

Code:  Logic hook makes a SOAP call, and then we display the result as follows:
$GLOBALS['log']->fatal('>>>>>' . $response, true); // ERROR HERE


Solution:
$response is returning a JSON object, so we need to escape the result as follows:
$GLOBALS['log']->fatal('>>>>>' . print_r($response, true));

SALESFORCE: Split Types

Error:
Validation Errors While Saving Record(s) There were custom validation error(s) encountered while saving the affected record(s). The first validation error encountered was "You do not have sufficient access to modify splits of this split type.


Solution:
Verify which fields are being used under Opportunity Split and set the correct permissions on that field.

1. Go to Setup->Customize->Opportunities->Opportunity Split->Settings
2. Check which fields are set to split
3. Go to the Opportunity object and set the correct security permissions for those fields

SALESFORCE: Permission Issues

Error:

"INVALID_FIELD: Select Id, Name from User Where ProfileId in ('') AND UserRoleId ^ ERROR at Row:1:Column:33 No such column 'ProfileId' on entity 'User'. If you are attempting to use a custom field, 
be sure to append the '__c' after the custom field name. Please reference your WSDL or 
the describe call for the appropriate names."

 
Solution:

Go to the Profile having the issue, and make sure "View Setup and Configuration" option is checked.

SUGARCRM: Package Deployment

Problem:

You get the following error when trying to deploy a new package from Admin:

"An error has occurred during deploying process, your package may not have installed correctly."

 Analyzing the logs, we get:

[FATAL] ERROR: rmdir_recursive(): argument  is not a file or a dir.

Solution:

Open config.php and make sure both group and user are set to the correct values.

array (
    'dir_mode' => 493,
    'file_mode' => 493,
    'user' => '',
    'group' => '',
  ),