Problem/Motivation
The following happened when I tried to install the module,
$ ddev composer require 'drupal/ckeditor5_plugin_pack:^1.3'
./composer.json has been updated
Running composer update drupal/ckeditor5_plugin_pack
Gathering patches for root package.
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/ckeditor5_plugin_pack ^1.3 -> satisfiable by drupal/ckeditor5_plugin_pack[1.3.0, 1.3.1, 1.3.2].
- drupal/ckeditor5_plugin_pack[1.3.0, ..., 1.3.2] require drupal/ckeditor5_premium_features ^1.3 -> satisfiable by drupal/ckeditor5_premium_features[1.3.0, ..., 1.4.2].
- drupal/ckeditor5_premium_features 1.3.0 requires drupal/core ^9.3 || ^10.0 -> found drupal/core[9.3.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.6.x-dev] but the package is fixed to 11.2.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/ckeditor5_premium_features[1.3.1, ..., 1.4.2] require openai-php/client ^0.4.0 || ^0.10.0 -> found openai-php/client[v0.4.0, ..., v0.10.3] but the package is fixed to v0.13.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
exit status 2
Composer [require drupal/ckeditor5_plugin_pack:^1.3] failed, composer command failed: exit status 2. stderr=
I followed Composer's suggestion to use -W option and I was able to install the module as follows,
$ ddev composer require 'drupal/ckeditor5_plugin_pack:^1.3' -W
./composer.json has been updated
Running composer update drupal/ckeditor5_plugin_pack --with-all-dependencies
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Lock file operations: 8 installs, 1 update, 0 removals
- Locking aws/aws-crt-php (v1.2.7)
- Locking aws/aws-sdk-php (3.346.2)
- Locking caxy/php-htmldiff (v0.1.17)
- Locking drupal/ckeditor5_plugin_pack (1.3.2)
- Locking drupal/ckeditor5_premium_features (1.4.2)
- Locking ezyang/htmlpurifier (v4.18.0)
- Locking firebase/php-jwt (v6.11.1)
- Locking mtdowling/jmespath.php (2.8.0)
- Downgrading openai-php/client (v0.13.0 => v0.10.3)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 8 installs, 1 update, 0 removals
- Downloading aws/aws-crt-php (v1.2.7)
- Downloading firebase/php-jwt (v6.11.1)
- Downloading ezyang/htmlpurifier (v4.18.0)
- Downloading caxy/php-htmldiff (v0.1.17)
- Downloading mtdowling/jmespath.php (2.8.0)
- Downloading aws/aws-sdk-php (3.346.2)
Gathering patches for root package.
Gathering patches for dependencies. This might take a minute.
- Installing aws/aws-crt-php (v1.2.7): Extracting archive
- Downgrading openai-php/client (v0.13.0 => v0.10.3): Extracting archive
- Installing firebase/php-jwt (v6.11.1): Extracting archive
- Installing ezyang/htmlpurifier (v4.18.0): Extracting archive
- Installing caxy/php-htmldiff (v0.1.17): Extracting archive
- Installing mtdowling/jmespath.php (2.8.0): Extracting archive
- Installing aws/aws-sdk-php (3.346.2): Extracting archive
- Installing drupal/ckeditor5_premium_features (1.4.2): Extracting archive
- Installing drupal/ckeditor5_plugin_pack (1.3.2): Extracting archive
7 package suggestions were added by new dependencies, use `composer suggest` to see details.
Generating optimized autoload files
56 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
The module is working after installation but I noticed that if I enable WProofreader, the editor will be broken that it won't load. This issue is reported in
WProofreader Plugin Issue
🐛
WProofreader Plugin Issue
Active
already. So I am not sure if the WProofreader issue is related to the way I installed the module or not.