Horizon Aid fails to install on Drupal CMS due to deprecated dependency

Problem/Motivation

Horizon Aid fails to install on Drupal CMS due to dependency on drupal_cms_admin_ui that has been deprecated.

Since Drupal CMS 2.2.3 (7 October 2026), a fresh composer create-project drupal/cms has drupal/tagify: ^2.0.4 in its root composer.json, unpacked from drupal_cms_site_template_base 2.2.3. Drupal CMS 2.2 removed drupal_cms_admin_ui, drupal_cms_content_type_base, drupal_cms_media and drupal_cms_privacy_basic from its 2.x branch. Their last releases, 2.1.6, require drupal/tagify ^1.2, directly or through drupal_cms_content_type_base. So every Vardot site template that still depends on them fails to install from the Drupal CMS installer.

Reported by xpete.

Steps to reproduce

Install Drupal CMS with "Horizon Aid" theme.
Error log:

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /core/install.php?rewrite=ok&langcode=pt-pt&profile=drupal_cms_installer&name=ludotempo&template=1&id=1&op=do_nojs&op=do
StatusText: OK
ResponseText: Symfony\Component\Process\Exception\ProcessFailedException: The command "'/usr/bin/php' '/home/username/public_html/drupalcms2/vendor/composer/./composer/bin/composer' '--no-interaction' 'require' 'drupal/horizonaid' '--minimal-changes' '--update-with-all-dependencies'" failed.
Exit Code: 2(Misuse of shell builtins)
Working directory: /home/username/public_html/drupalcms2
Output:
================
Error Output:
================
./composer.json has been updated
Running composer update drupal/horizonaid --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/horizonaid * -> satisfiable by drupal/horizonaid[1.0.0, ..., 1.0.5].
- drupal/drupal_cms_admin_ui[2.0.0, ..., 2.1.6] require drupal/tagify ^1.2 -> found drupal/tagify[1.2.0, ..., 1.2.55] but it conflicts with your root composer.json require (^2.0.4).
- drupal/horizonaid[1.0.0, ..., 1.0.5] require drupal/drupal_cms_admin_ui ~2 -> satisfiable by drupal/drupal_cms_admin_ui[2.0.0, ..., 2.1.6].
You can also try re-running composer require with an explicit version constraint, e.g. "composer require drupal/horizonaid:*" to figure out if any version is installable, or "composer require drupal/horizonaid:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
in Symfony\Component\Process\Process->mustRun() (line 289 of /home/xpete/public_html/drupalcms2/vendor/symfony/process/Process.php).

The same from the command line: composer create-project drupal/cms, then composer require drupal/horizonaid.

Proposed resolution

Removing drupal_cms_admin_ui from the dependencies, as first proposed, is not enough. Tested on a fresh Drupal CMS 2.2.3: composer then fails on varbase_content_base (drupal/tagify ~1.0), and after widening that, on varbase_page_base (drupal_cms_content_type_base ^2). Our recipes also rely on what the removed recipes set up, so each piece moves into the Varbase recipe whose domain it is:

• Varbase Content Base: #3629373: Allow Tagify 2 and carry the content basics from the removed drupal_cms_content_type_base
• Varbase Editor Base: #3629374: Ship the content_format and Canvas text formats instead of relying on drupal_cms_content_type_base
• Varbase Media Base: #3629376: Carry the media setup from the removed drupal_cms_media
• Varbase Security Base: #3629377: Install and configure Klaro instead of relying on the removed drupal_cms_privacy_basic
• Varbase Admin Base: #3629379: Carry the admin UI from the removed drupal_cms_admin_ui
• Varbase Page Base: #3629381: Stop requiring the removed drupal_cms_content_type_base
• Educare: #3629382: Educare fails to install on Drupal CMS 2.2.3: stop requiring the removed drupal_cms recipes
• The Rightup: #3629384: The Rightup fails to install on Drupal CMS 2.2.3: stop requiring the removed drupal_cms recipes
• Varbase Starter: #3629385: Varbase Starter fails to install on Drupal CMS 2.2.3: stop requiring the removed drupal_cms recipes

Here in Horizon Aid: drop drupal_cms_admin_ui, drupal_cms_media and drupal_cms_privacy_basic from composer.json and recipe.yml.

drupal.org lists drupal_cms_admin_ui (and the other three) as replaced by Drupal CMS Basics (drupal_cms_site_template_base). Varbase does not switch to that recipe here: applied first, it would take over Varbase's own metatag defaults and the page and media displays (20 configuration items differ). The Varbase recipes carry the same pieces instead, varbase_admin_base standing in for drupal_cms_admin_ui.

Tested with these changes: on a fresh Drupal CMS 2.2.3 with Tagify 2.0.4, Horizon Aid resolves and installs by drush and through the browser installer, and Educare, The Rightup and Varbase Starter install by drush. None of the removed recipes are pulled in. On Varbase (drupal/varbase_project 11.0.x-dev), Horizon Aid installs by drush.

Remaining tasks

• ✅ File an issue
• ✅ Addition/Change/Update/Fix
• ✅ Testing to ensure no regression
• ➖ Automated unit testing coverage
• ✅ Automated functional testing coverage
• ➖ UX/UI designer responsibilities
• ➖ Readability
• ➖ Accessibility
• ➖ Performance
• ➖ Security
• ➖ Developer Documentation
• ➖ User Guide Documentation
• ❌ Reviewed by human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ✅ Credit contributors
• ❌ Review with the product owner
• ✅ Release notes snippet
• ✅ Release Horizon Aid 1.0.6
• ✅ Merge and release the related Varbase recipe issues first

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• Released in Horizon Aid 1.0.6.

AI-Generated: Yes