Skip to content

59 · Base recipe 2.2.3 requires Tagify 2, so 11 site templates cannot be installed

Project Drupal CMS (drupal_cms), site template base recipe (drupal_cms_site_template_base) – and 11 site templates
Component Recipes (composer.json)
Category Bug report
Priority Critical
Status Reported upstream as #3591492

Workaround and open tasks (2026-10-10)

The Drupal CMS German Installer keeps the base recipe at 2.2.2 while it requires Tagify 2 (installer_de_patch.sh, pin_template_base_for_tagify()); Composer then picks Tagify 1.2.55. Remove the workaround once Drupal CMS allows Tagify 1.2 again or the templates allow Tagify 2. The workaround does not switch itself off.

Seven templates have no GitLab work items; their reports go through the drupal.org form (texts in ~/work/c-2026-10-10-tagify-reports/tagify-meldungen.html): CareSphere, Convene, Goodwell, Hourglass Corporate, Local, Provus EDU, Pulse – see the table below.

Problem/Motivation

Issue #3591486 ("Allow Tagify 2.0.x in drupal_cms_site_template_base") changed the constraint in recipes/drupal_cms_site_template_base/composer.json from "drupal/tagify": "^1.2" to "^2.0.4". That allows Tagify 2, but it also rules out Tagify 1.2. Eleven site templates of the official list still require Tagify 1.2 in their latest release and default branch, so since Drupal CMS 2.2.3 Composer finds no solution and the installer stops as soon as one of them is chosen.

Site template Requires Filed
Archimedes ^1.2.50 #3582062
CareSphere ^1.2.50 –
Convene ^1.2.50 –
Convivial Gov ^1.2.54 #3582426
Goodwell ^1.2.51 –
Healthcare ^1.2.50 #3611915
Hourglass Corporate ^1.2.51 –
Local ^1.2.50 –
Provus EDU ^1.2.51 –
Pulse ^1.2.50 –
Summit ^1.2 #3612846

The other templates (Byte, Haven, Everbright, Forma, Mercury Demo, Dashi, Meridian Charter, Varbase Starter, The Rightup, Educare, Horizon Aid) still install. Lupus Decoupled Starter fails for an unrelated reason (report 13).

Composer's message is misleading: it says Tagify 1.2.x "were not loaded, because they are affected by security advisories". With the advisory block turned off, the same request still fails ("conflicts with another require"); the actual conflict is the base recipe's ^2.0.4. Tagify 1.2.52 and later are not affected by any advisory (SA-CONTRIB-2026-043 covers <1.2.52).

Steps to reproduce

  1. composer create-project drupal/cms (2.2.3).
  2. In the installer, choose e.g. CareSphere, or run composer require drupal/caresphere.
  3. Composer cannot resolve the dependencies; the installer shows "An error occurred".

Proposed resolution

Allow both major versions, as the title of #3591486 says:

-        "drupal/tagify": "^2.0.4",
+        "drupal/tagify": "^1.2.52 || ^2.0.4",

tagify_user_list (used since #3591489) and its settings exist in Tagify 1.2.55 as well. The templates use only widgets that both major versions provide (tagify_entity_reference_autocomplete_widget, tagify_select_widget). The templates should allow ^1.2.52 || ^2.0 (reported to each of them, see the table).

A check in CI that requires every template of site-templates.yml on the current base recipe would catch this kind of break before a release.

Additional information

Found on 2026-10-10 when CareSphere could not be installed. With the base recipe kept at 2.2.2, CareSphere installs without errors (local run of the web installer job).

Copy to drupal.org

Issue title:

Base recipe 2.2.3 requires Tagify 2, so 11 site templates cannot be installed

Issue summary (paste it into the "Issue summary" field; project, component, category and priority are in the table above):

<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>Issue #3591486 ("Allow Tagify 2.0.x in drupal_cms_site_template_base") changed the constraint in <code>recipes/drupal_cms_site_template_base/composer.json</code> from <code>"drupal/tagify": "^1.2"</code> to <code>"^2.0.4"</code>. That allows Tagify 2, but it also rules out Tagify 1.2. Eleven site templates of the official list still require Tagify 1.2 in their latest release and default branch, so since Drupal CMS 2.2.3 Composer finds no solution and the installer stops as soon as one of them is chosen.</p>
<table>
<thead>
<tr>
<th>Site template</th>
<th>Requires</th>
<th>Filed</th>
</tr>
</thead>
<tbody>
<tr>
<td>Archimedes</td>
<td><code>^1.2.50</code></td>
<td><a href="https://git.drupalcode.org/project/archimedes/-/work_items/3582062">#3582062</a></td>
</tr>
<tr>
<td>CareSphere</td>
<td><code>^1.2.50</code></td>
<td>–</td>
</tr>
<tr>
<td>Convene</td>
<td><code>^1.2.50</code></td>
<td>–</td>
</tr>
<tr>
<td>Convivial Gov</td>
<td><code>^1.2.54</code></td>
<td><a href="https://git.drupalcode.org/project/convivial_gov/-/work_items/3582426">#3582426</a></td>
</tr>
<tr>
<td>Goodwell</td>
<td><code>^1.2.51</code></td>
<td>–</td>
</tr>
<tr>
<td>Healthcare</td>
<td><code>^1.2.50</code></td>
<td><a href="https://git.drupalcode.org/project/healthcare/-/work_items/3611915">#3611915</a></td>
</tr>
<tr>
<td>Hourglass Corporate</td>
<td><code>^1.2.51</code></td>
<td>–</td>
</tr>
<tr>
<td>Local</td>
<td><code>^1.2.50</code></td>
<td>–</td>
</tr>
<tr>
<td>Provus EDU</td>
<td><code>^1.2.51</code></td>
<td>–</td>
</tr>
<tr>
<td>Pulse</td>
<td><code>^1.2.50</code></td>
<td>–</td>
</tr>
<tr>
<td>Summit</td>
<td><code>^1.2</code></td>
<td><a href="https://git.drupalcode.org/project/summit/-/work_items/3612846">#3612846</a></td>
</tr>
</tbody>
</table>
<p>The other templates (Byte, Haven, Everbright, Forma, Mercury Demo, Dashi, Meridian Charter, Varbase Starter, The Rightup, Educare, Horizon Aid) still install. Lupus Decoupled Starter fails for an unrelated reason (report 13).</p>
<p>Composer's message is misleading: it says Tagify 1.2.x "were not loaded, because they are affected by security advisories". With the advisory block turned off, the same request still fails ("conflicts with another require"); the actual conflict is the base recipe's <code>^2.0.4</code>. Tagify 1.2.52 and later are not affected by any advisory (SA-CONTRIB-2026-043 covers <code><1.2.52</code>).</p>
<h3 id="summary-steps-reproduce">Steps to reproduce</h3>
<ol>
<li><code>composer create-project drupal/cms</code> (2.2.3).</li>
<li>In the installer, choose e.g. CareSphere, or run <code>composer require drupal/caresphere</code>.</li>
<li>Composer cannot resolve the dependencies; the installer shows "An error occurred".</li>
</ol>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Allow both major versions, as the title of #3591486 says:</p>
<code>-        "drupal/tagify": "^2.0.4",
+        "drupal/tagify": "^1.2.52 || ^2.0.4",</code>
<p><code>tagify_user_list</code> (used since #3591489) and its settings exist in Tagify 1.2.55 as well. The templates use only widgets that both major versions provide (<code>tagify_entity_reference_autocomplete_widget</code>, <code>tagify_select_widget</code>). The templates should allow <code>^1.2.52 || ^2.0</code> (reported to each of them, see the table).</p>
<p>A check in CI that requires every template of <code>site-templates.yml</code> on the current base recipe would catch this kind of break before a release.</p>
<h3>Additional information</h3>
<p>Found on 2026-10-10 when CareSphere could not be installed. With the base recipe kept at 2.2.2, CareSphere installs without errors (local run of the web installer job).</p>