- Issue created by @phenaproxima
- π¬π§United Kingdom alexpott πͺπΊπ
phenaproxima β credited alexpott β .
- π¬π§United Kingdom alexpott πͺπΊπ
It'd be great if this could make it's way back to 1.0.x releases too.
But this is perfect.
- πΊπΈUnited States phenaproxima Massachusetts
Yeah, this will get into 1.0.x as a special exception, since without that there's almost no point to the fix!
-
phenaproxima β
committed 9a20c599 on 1.1.x
Issue #3514198 by phenaproxima, alexpott, donm: It is impossible to...
-
phenaproxima β
committed 9a20c599 on 1.1.x
- πΊπΈUnited States phenaproxima Massachusetts
Merged into 1.1.x and cherry-picked to 1.0.x. The 1.x branch is already using the ^ operator so no change was needed there. I will release drupal_cms_starter 1.0.4 with this change!
-
phenaproxima β
committed a9b20a4d on 1.0.x
Issue #3514198 by phenaproxima, alexpott, donm: It is impossible to...
-
phenaproxima β
committed a9b20a4d on 1.0.x
- πΊπΈUnited States phenaproxima Massachusetts
Released https://www.drupal.org/project/drupal_cms_starter/releases/1.0.4 β with this fix. That should allow you to update Drupal CMS Olivero! Thanks for catching this.
- π¬π§United Kingdom alexpott πͺπΊπ
Still can't update to it via the UI because the updater won't update recipes :)
Problem 1 - Root composer.json requires drupal/drupal_cms_olivero 1.1.0 (exact version match: 1.1.0 or 1.1.0.0), found drupal/drupal_cms_olivero[1.1.0] but these were not loaded, likely because it conflicts with another require. Problem 2 - drupal/drupal_cms_starter is locked to version 1.0.2 and an update of this package was not requested. - drupal/drupal_cms_starter 1.0.2 requires drupal/drupal_cms_olivero ~1.0.1 -> found drupal/drupal_cms_olivero[1.0.1, 1.0.3] but it conflicts with your root composer.json require (1.1.0).
But at least composer update from the CLI now gets me to the latest theme release and should solve the problem for a while.
- πΊπΈUnited States phenaproxima Massachusetts
π€ What's weird about that, to me, is that Package Manager does
composer update --with-all-dependencies
, which should, I'd think, get around that: https://git.drupalcode.org/project/automatic_updates/-/blob/3.0.x/packag...But I guess a reasonable workaround would be to run
composer update drupal/drupal_cms_starter
at the command line first, before trying to update the theme in the UI.To ease things somewhat, I have marked the 1.0.x version of the theme as supported, but not recommended. So at least folks won't get any more warnings in the UI about having unsupported extensions installed.