Disabling modules that block sites on Acquia Cloud

Issue

Drupal fails to run on Acquia Cloud.

Resolution

A common reason is that a custom Drupal module that won't run on Acquia Cloud. If you know which module is causing the problem, you can disable the module using Drush or directly in MySQL.

Disable a module via Drush

Important

Create a database backup prior to any significant change to a website, including disabling or enabling modules.  

• Connect to your server using SSH.
• Run one of the following Drush command to disable the module:
  Drupal 7:
  copy

  drush @[site].[env] pm-disable [module]

  Drupal 8/9:

  copy

  drush @[site].[env] pm-uninstall [module]

  Where [site] is your Acquia Cloud site name, [env] is the environment that you're updating (example values are dev, test, and prod), and [module] is the name of module that you want to disable.

Disable a module via MySQL

Alternatively, you can disable the module manually in the database on your Acquia Cloud server.

Important

The MySQL command should only be used as a last resort, and after taking a database backup. It will not disable any modules that are dependent on the module you're attempting to disable, causing more errors.

• Connect to your server using SSH.
• Open a connection to your database using the following command:
  copy

  drush @[site].[env] ah-sql-cli

  Where [site] is your Acquia Cloud site name, and [env] is the environment that you're updating (example values are dev, test, and prod).

• Disable the module with this SQL command:
  copy

  UPDATE system SET status='0' WHERE name='[module]';

  Where [module] is the name of module that you want to disable.