Health Check Error: Module Has Definition of Another Module

Overview

The Health Check wizard must be run when upgrading to evaluate whether your instance is suitable for upgrade. During the health check, various types of issues may be detected which can affect your ability to upgrade to Sugar 7.x. This article will cover how to resolve a "Module has definition of another module" error reported by the health check.

Symptoms

This error generates an output similar to the following in health check:

Resolution

The generated error message will help determine the contents of the file causing the health check error. To address this issue, the code-level customization will need to be edited from Sugar before proceeding with the upgrade to Sugar 7. The following sections will cover potential scenarios which can trigger this error and how to resolve it properly.

File References Another Module

The ./custom/Extension/modules/Leads/Ext/Vardefs/account_name.php file contains references to another module (e.g. Opportunity):

<?php
  $dictionary['Opportunity']['fields']['account_name']['required'] = false;
  unset($dictionary['Opportunity']['fields']['account_name']['importable']);
?>

To address this issue, you will need to disable the file by placing it in a "Disabled" directory (e.g. ./custom/Extension/modules/Leads/Ext/Vardefs/Disabled) contained within the current directory of the file. In this example, the new directory path for the offending file would be: ./custom/Extension/modules/Leads/Ext/Vardefs/Disabled/account_name.php.

File References Another Module in Addition to Current Module

The ./custom/Extension/modules/Leads/Ext/Vardefs/account_name.php file contains references to another module (e.g. Opportunity) in addition to the current module (e.g. Leads). To address this issue, you will need to create a backup of the file, edit the original file, and remove the line of code referencing the other module (e.g. Opportunity).

The ./custom/Extension/modules/Leads/Ext/Vardefs/account_name.php file contains the following lines of code:

<?php
  $dictionary['Opportunity']['fields']['account_name']['required'] = false;
  unset($dictionary['Opportunity']['fields']['account_name']['importable']);

  $dictionary['Lead']['fields']['first_name']['required'] = false;
  unset($dictionary['Lead']['fields']['first_name']['importable']);
?> 

Create a backup of this file as ./custom/Extension/modules/Leads/Ext/Vardefs/account_name.php.bak then edit the original file to remove any lines of code referring to other modules. Save the file.

The corrected file should then look similar to this:

<?php
  $dictionary['Lead']['fields']['first_name']['required'] = false;
  unset($dictionary['Lead']['fields']['first_name']['importable']);
?> 

Once the necessary change has been made, please navigate to Admin > Repair and perform "Quick Repair and Rebuild" to ensure that the changes are synced between the application and database.

Perform the health check again to confirm that the error is no longer reported.