Manually Removing Module Loader Packages

Aug 15, 2017    Janaki Mahapatra, Sugar
Use the following steps to remove the reference to the package in the Sugar file system:
  1. Navigate to the ./upload/upgrades/module/ directory.
  2. Create a new directory titled "disabled".
  3. Move the files that are related to the specific package into the newly created "disabled" directory.
    • For our example, the following files would be moved into the "disabled" directory:
      • debug_marketo-manifest.php
      • debug_marketo.zip
Additionally, you will need to ensure the module is fully disabled in your instance.
  1. Navigate to the ./custom/Extension/application/Ext/Include/ directory.
  2. Create a new directory titled "Disabled" if one does not already exist.
  3. Open any files in the Include directory and if the file references the module you are attempting to remove, transfer the file to the Disabled directory.
  4. In Sugar, go to Admin > Repair > Quick Repair and Rebuild to rebuild the Extension directory with the changes you made.
Note: There may be additional files that remain as part of the module once the module is disabled. If this the case, rerunning the health check should identify any additional critical files that will need to be disabled. Once the appropriate files are moved to the "disabled" directory, the database reference will need to be removed. Please use the following steps to remove the database reference:
  1. Use the following query to select the records in the upgrade_history table that match the name of the package:
    • SELECT * FROM upgrade_history WHERE filename LIKE '%/%';
    • For our example, the query would be: SELECT * FROM upgrade_history WHERE filename LIKE '%/debug_marketo.zip%';
  2.  Delete the returned records from the upgrade_history table.
Navigate back to Module Loader to confirm that the packages no longer appear. Note: Copied from http://support.sugarcrm.com/Knowledge_Base/Module_Loader/Manually_Removing_Module_Loader_Packages/