If you start evaluating AI recipes

1) install https://www.drupal.org/project/ai_recipe_llm_optimized_content -> success
2) install https://www.drupal.org/project/ai_recipe_seo_optimizer -> leads to a dependency conflict

composer require drupal/ai_recipe_seo_optimizer
./composer.json has been updated
Running composer update drupal/ai_recipe_seo_optimizer
> Drupal\Composer\Composer::ensureComposerVersion
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/ai_recipe_seo_optimizer * -> satisfiable by drupal/ai_recipe_seo_optimizer[0.1.0, 0.x-dev].
    - drupal/ai_recipe_seo_optimizer[0.1.0, ..., 0.x-dev] require drupal/drupal_cms_seo_tools ^2.x-dev -> satisfiable by drupal/drupal_cms_seo_tools[2.x-dev].
    - drupal/drupal_cms_seo_tools 2.x-dev requires drupal/bpmn_io ^3 -> found drupal/bpmn_io[dev-3.0.x, 3.0.0-alpha1, ..., 3.0.x-dev (alias of dev-3.0.x)] but the package is fixed to 2.0.10 (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.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require drupal/ai_recipe_seo_optimizer:*" to figure out if any version is installable, or "composer require drupal/ai_recipe_seo_optimizer:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

not sure if this has to be solved here, in ai_recipe_llm_optimized_content or elsewhere

Issue fork ai_recipe_seo_optimizer-3552955

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

dasjo created an issue. See original summary.

thejimbirch’s picture

thejimbirch commented

Since the other recipe requires a Drupal CMS recipe like this:

"drupal/drupal_cms_content_type_base": "^1.2 || ^2.0",

And 1.2 is stable, you got that. While this recipe is just ^2 and that requires the latest version of ECA.

I will try to see if this recipe works on 1.2

thejimbirch opened merge request !8

thejimbirch’s picture

thejimbirch commented
Status: Active » Needs review

See if that works for you.

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented

thanks! i tried to test it but didn't get it to work. based on this article
https://www.drupal.org/docs/develop/using-composer/tricks-for-using-comp...

tried
composer require drupal/ai_recipe_seo_optimizer:@dev-3552955-installation-blocked-due

without much luck. maybe there is an easier way to test this that i am not aware of

thejimbirch’s picture

thejimbirch commented

Its a simple change in the composer file. You could edit your local file to match https://git.drupalcode.org/project/ai_recipe_seo_optimizer/-/merge_reque...