Contrib.social

Conflict with acquia_cms profile

Open on Drupal.org →
Created on 23 August 2023, about 1 year ago
Updated 10 October 2023, about 1 year ago

Problem/Motivation

Not able to run database updates because of dependency conflict with acquia_cms profile.

Steps to reproduce

When using both acquia_cms version: 1.5.5, and acquia_cms_common version: 2.1.7 (due to being on D9.5.x still).
NOTE: obviously you can't just install acquia_cms_common at the version mentioned, you have to need to run the update, and installing the module at the version mentioned here will mean the highwater mark is set - and the update won't run. So either start with a lower version and then update, or just roll your highwater mark back one number (so the update will run).

Visit /update.php or run drush updb.

Proposed resolution

Situation is:

/profiles/contrib/acquia_cms/acquia_cms.info.yml

name: Acquia CMS
core_version_requirement: ^9
version: '1.5.5'
...
dependencies:
...
  - purge:purge_processor_lateruntime

acquia_cms_common.install

/**
 * Implements hook_update_N().
 *
 * Uninstall Late runtime processor module.
 */
function acquia_cms_common_update_8007() {
  if (\Drupal::moduleHandler()->moduleExists('purge_processor_lateruntime')) {
    // Uninstall purge_processor_lateruntime module.
    \Drupal::service('module_installer')->uninstall(['purge_processor_lateruntime']);
  }
}

Which results in a fatal error.

The commits relate to: https://git.drupalcode.org/project/acquia_cms_common/-/commit/e5662b8c7e...

Which is titled "Merge branch '3.x' into HEAD" and, given this is the 2.x branch - I need to know if the wrong thing has been committed here? If not, then I will raise this as an issue against the acquia_cms profile instead.

🐛 Bug report
Status

Active

Version

2.1

Component

Code

Created by

🇬🇧United Kingdom pobster

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @pobster
  • Comment about 1 year ago →
    🇬🇧United Kingdom pobster
  • Comment about 1 year ago →
    🇬🇧United Kingdom pobster
  • Comment about 1 year ago →
    🇮🇳India sahal_va

    I have similar issue after updating this module. Did you find any solution/workaround ? @pobster

  • Comment about 1 year ago →
    🇬🇧United Kingdom pobster

    Hiya!

    I've left it with Acquia (who I don't mind saying, were really useless with it) - but yes, there are three solutions.

    1. You can convert your acquia_cms profile to instead be the "minimal" profile.
    That way the dependency will come from your own core.extension.yml and not the acquia_cms profile.
    2. If you do need/ use purge_processor_lateruntime, edit the acquia_cms_common.install file to:

    /**
 * Implements hook_update_N().
 *
 * Uninstall Late runtime processor module.
 */
function acquia_cms_common_update_8007() {
  // Just mark this update as having been "run".  This way it won't be run again.
}

    3. If you don't need the purge_processor_lateruntime module installed, edit profiles/contrib/acquia_cms/acquia_cms.info.yml and remove this line:

    - purge:purge_processor_lateruntime

  • Assigned to rajeshreeputra
  • Comment about 1 year ago →
    🇮🇳India rajeshreeputra Pune
  • Issue was unassigned.
  • Comment about 1 year ago →
    🇮🇳India rajeshreeputra Pune
contrib.social Blog FAQ Discussions
Production build 0.71.5 2024