CiviCRM Stack Exchange is a question and answer site for administrators and users of the CiviCRM Constituent Relationship Management software. It only takes a minute to sign up.
Sign up to join this community
From an existing site set up using the roundearth composer plugin method as detailed -> https://www.mydropwizard.com/blog/better-way-install-civicrm-drupal-8
composer create-project roundearth/drupal-civicrm-project:8.x-dev some-dir --no-interaction
How do I update this to use the newer https://lab.civicrm.org/dev/drupal/snippets/43composer require civicrm/civicrm-asset-plugin:'~1.0.0' pear/pear_exception:'1.0.1 as 1.0.0' civicrm/civicrm-{core,packages,drupal-8}:'^5.25' --prefer-source
Depending on how your initial site set up was created you might need to take a more extreme option detailed below but hopefully the following will work:
If you want you can copy composer.json , composer.lock to a new directory (or local) and use issue composer installto check the below works this can be useful if you are having problems and need to remove composer.lock and vendor. But I'm assuming you are going to be doing this on dev/staging.
composer remove roundearth/civicrm-composer-plugin --no-update
composer config extra.enable-patching true
civicrm/civicrm-{core,packages,drupal-8}:'^[civicrm latest version without the point version]'
Apart from the removal of the roundearth/civicrm-composer-plugin you want to follow the install steps outlined here: https://docs.civicrm.org/installation/en/latest/drupal8/
(Note D9 Drupal recommended you'll need to set the minimum stability from stable to dev if you haven't already).
If you are still on an older version of civicrm you might need to include pear/pear_exception:'1.0.1 as 1.0.0' in the above require. But the latest version doesn't require this anymore.
Assuming this is successful you will then want to drush updb drush cr
I'd also recommend clearing out web/libraries/civicrm/ and then repopulating with composer civicrm:publish
This is something you might need to repeat on live.
Note hopefully soon "pear/pear_exception:'1.0.1 as 1.0.0'" will not be required. Check the install instructions and mirror them.
Options to make things easier.
As per below check your civicrm.settings.php file and make sure the following are either removed or match the location where the libraries are stored.
$civicrm_paths['civicrm.root']['url'] = '/libraries/civicrm/';
$civicrm_paths['civicrm.packages']['url'] = '/libraries/civicrm/packages/';
The extreme version below assumes you have no custom themes/modules or file uploads. If you have any of the above. You probably want to follow a different root!
I had done this once and I described it at https://lab.civicrm.org/dev/drupal/-/issues/115#note_34161
<one folder up from root>composer create-project drupal/recommended-project:8.x.y <root folder><into root folder>export COMPOSER_MEMORY_LIMIT=-1 for unix) $civicrm_paths['civicrm.root']['url'] = '/libraries/civicrm/';
$civicrm_paths['civicrm.packages']['url'] = '/libraries/civicrm/packages/';
CAVEAT: As described in that thread it really depends where you started from and additionally what else you have installed via composer on that site and so you might not want to remove the whole drupal folder. The above was a pretty plain stock site and I was also converting to drupal-recommended at the same time. If you keep some things and for example if you've installed fancy modules, you may see composer throwing up irreconcilable differences.
Also the above was for a dev install, using dev-master. Replace dev-master with a specific 5.x.y or ^5.x as desired.
Further disclaimer: Civi + d8 has been a constantly moving target. It's repeatedly come up that what worked "2 months ago" doesn't quite work "now". I have not tried the above in the last 2 months.
