New answers tagged

0

In a similar situation inside a lando (docker local developement environment) I was able to overcome this problem by getting a new personal_access_tokens from https://gitlab.com/-/profile/personal_access_tokens and running lando composer config -g gitlab-oauth.gitlab.com glpat-XXXXXXXXXXXXXXXXXXXXX


1

Thank you @clive and @jaypan. Downgrading Composer to ver. 1.10.23 brought up a "run out of memory" error, which I wouldn't have noticed beforehand. Ultimately the Composer version was not the error. @clive you were right, php_mbstring WAS not installed on this server, for some reason, and is installed on the DEV server. Once installed, both ...


2

I tried composer update to verify that composer will work when the time comes. To verify if it will work when the time comes, you would want to run composer install. This will attempt to install the set of dependencies according to what is listed in the composer.lock file. Running composer update attempts to update all your modules to the newest versions. ...


1

There was a bug in upgrade_status that didn't treat profiles (like drupalcommerce/project-base ) as they should be. But instead treated it like a misbehaving module. This is fixed in this issue: https://www.drupal.org/project/upgrade_status/issues/3230266 So you can try the patch from that issue, or wait for a new release which includes the patch.


0

Here's how I managed to upgrade from 8.9.20 to 9.2.9 You need to add to your composer.json : "repositories": { "drupal": { "type": "composer", "url": "https://packages.drupal.org/8" }, "commerce_base": { "type": "vcs", "url": "https:/...


3

Let's think about what is actually going on here. With XAMPP, you are basically running an Apache server inside a Windows program. With WSL v1, you have a Linux virtual machine running within Windows that has drush, composer, etc. With WSL v2, you have Linux running in Hyper-V (MS hypervisor), so you get near-native Linux performance with less virtualization ...


0

Errors like that mean that the installing package requires other dependencies, so you can always use the -W flag to install the package with dependencies. composer global require drush/drush:8.x -W


2

You might want to have a look at the documentation on drupal.org: Using Composer to Install Drupal and Manage Dependencies Building a Drupal site with Git It's a lot to digest, but it goes into quite some detail on how to use composer and git to manage your site. The gist of it is this: You use composer to download code (modules, themes, libraries, ...) ...


1

As is usually the fix, deleting the vendor folder and composer.lock file and then running: composer require drupal/core-recommended:8.9.16 --update-with-dependencies seems to have fixed the problem. Since I deleted the .lock file it effectively runs a composer update which updated a few of the contrib modules. Not what i wanted; but I could have locked ...


Top 50 recent answers are included