Automated Drupal 10 compatibility fixes

This worked great in some quick testing I did using the find/replace plugin. I didn't test all of the plugins, but it should be a good start.

Hi,

Feeds_Tamper.Dev didn't install in latest Drupal 10 through composer, PHP 8.1
composer require 'drupal/feeds_tamper:2.x-dev@dev'
Error

Problem 1
    - drupal/feeds_tamper dev-2.x requires drupal/tamper ^1.0-alpha3 -> found drupal/tamper[dev-1.x, 1.0.0-alpha3, 1.x-dev (alias of dev-1.x)] but it does not match your minimum-stability.
    - drupal/feeds_tamper 2.x-dev is an alias of drupal/feeds_tamper dev-2.x and thus requires it to be installed too.
    - Root composer.json requires drupal/feeds_tamper 2.x-dev@dev -> satisfiable by drupal/feeds_tamper[2.x-dev (alias of dev-2.x)].

Greetings, Martijn

Hi,
with latest version 10 still

composer require 'drupal/feeds_tamper:*'
Info from https://repo.packagist.org: #StandWithUkraine
./composer.json has been updated
Running composer update drupal/feeds_tamper
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/feeds_tamper *, found drupal/feeds_tamper[dev-2.x, 2.0.0-beta1, 2.0.0-beta2, 2.0.0-beta3, 2.x-dev (alias of dev-2.x)] but it does not match your minimum-stability.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

How can I resolve this, shouldn't first the patch be committed?
Thanks for your reply in advance, Greetings,

Hi,
I resolved this through stability
I had to set the stability to 'dev' and then the module installed through composer.
Greetings,

@summit
Yes, because Feeds Tamper has no stable release yet, the stability setting in composer.json can prevent the module from getting installed through composer.

I'm getting the following error when trying to install feeds_tamper.

I'm running Drupal 10.1.8 and Feeds 8.x-3.0-beta4.

Please let me know if there is any additional information that would be helpful.

composer require 'drupal/feeds_tamper:^2.0@beta'

./composer.json has been updated
Running composer update drupal/feeds_tamper
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/feeds_tamper 2.0.0-beta1 requires drupal/core ^8.5.0 -> found drupal/core[8.5.0, ..., 8.9.20] but the package is fixed to 10.1.8 (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/feeds_tamper 2.0.0-beta2 requires drupal/core ^8 || ^9 -> found drupal/core[8.0.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 10.1.8 (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/feeds_tamper 2.0.0-beta3 requires drupal/tamper ^1.0-alpha3 -> found drupal/tamper[dev-1.x, 1.0.0-alpha3, 1.0.0-alpha4, 1.x-dev (alias of dev-1.x)] but it does not match your minimum-stability.
    - Root composer.json requires drupal/feeds_tamper ^2.0@beta -> satisfiable by drupal/feeds_tamper[2.0.0-beta1, 2.0.0-beta2, 2.0.0-beta3].

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.

@_San_
I think that the minimum stability setting in your composer.json could be the issue. Since Tamper → is in alpha, that setting would need to be alpha in order to resolve that dependency of Feeds Tamper.

So in composer.json, you would need to have this:

"minimum-stability": "alpha",

You could also require the Tamper module separately, I think that would work as well. Then you would have these commands:

composer require drupal/tamper:^1.0@alpha
composer require drupal/feeds_tamper:^2.0@beta

That could be a better choice if you rather not would use modules that do not have a stable release yet. The reason that Tamper does not have a stable release yet, is because not all plugins available in the D7 version are ported yet.

Drupal 10 is out for some time now, and we now have an issue for D11 compatibility, so this issue can be closed.
📌 Automated Drupal 11 compatibility fixes for feeds_tamper Active

Automatically closed - issue fixed for 2 weeks with no activity.