Contrib.social

Install fails with commerce kickstart

Open on Drupal.org →
Created on 19 October 2024, 2 months ago

Problem/Motivation

I am using commerce kickstart and there are various commerce modules which are using layout builder restrictions module.

When I run composer, i see this error

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/vlsuite ^2.2 -> satisfiable by drupal/vlsuite[2.2.0, 2.x-dev].
    - drupal/vlsuite[2.2.0, ..., 2.x-dev] require drupal/layout_builder_restrictions ^3.0 -> found drupal/layout_builder_restrictions[dev-3.x, 3.0.0, 3.x-dev (alias of dev-3.x)] but the package is fixed to 2.20.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.

What should I do now?

💬 Support request
Status

Active

Version

2.2

Component

Miscellaneous

Created by

🇵🇰Pakistan ugintl

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @ugintl
  • Comment 2 months ago →
    CRZDEV

    Hello ugintl!
    Could you please add link to the commerce kickstart used project & specify its version?
    According to provided output, your composer.lock has defined layout_builder_restrictions:2.20.0, & vlsuite for core ^10.3 || ^11 (2.2.0) requires layout builder restrictions ^3.0.
    So try to require that version first "composer require 'drupal/layout_builder_restrictions:^3.0'" or install vlsuite with "-W or --with-all-dependencies" so all dependecies are updated to correct minimum version.

  • Comment about 2 months ago →
    🇵🇰Pakistan ugintl

    https://github.com/centarro/commerce_kickstart

    I have also created an issue on drupal https://www.drupal.org/project/commerce_kickstart →

    The latest version is 3.0

    The work around as you said is to update composer.json file to use version 3 of layout builder restrictions, but when there is an update to commerce kickstart, it will come back to its original. Isn't it so?

  • Comment about 2 months ago →
    CRZDEV

    In that case commerce kickstart should update that dependency version, as layout_builder_restrictions ^3.0 is the sugested by mantainers & also is compatible with core 11. So great that you created https://www.drupal.org/project/commerce_kickstart/issues/3481898 📌 Update layout builder restrictions to version 3 Active

  • Comment about 2 months ago →
    🇵🇰Pakistan ugintl

    Welcome. Ok so I have to wait? I am really excited to see vlsuite in action

  • Comment about 2 months ago →
    CRZDEV

    You can use 1.x version of vlsuite (suported for now but with some changes from 2.x):
    composer require 'drupal/vlsuite:^1.2' (for initial setup enable vlsuite_shuttle instead vlsuite_demo in that version). Then you should be able to update to 2.x without any problems when all dependencies are adjusted.

    Or help with PR / issue into commerce_kickstart issue with change "drupal/layout_builder_restrictions": "^2.12" for "drupal/layout_builder_restrictions": "^3.0".

    Great that you are interested! You can see a demo replicating drupal.org homepage here

  • Comment about 2 months ago →
    🇵🇰Pakistan ugintl

    What are the main differences between V1 and V2?

  • Comment about 2 months ago →
    CRZDEV

    Core compatibillity & vlsuite_demo / vlsuite_shuttle, 1.x will be end-of-life in future

  • Comment about 2 months ago →
    🇵🇰Pakistan ugintl

    I see that vlsuite_shuttle disables itself after doing its work, but does not remove anything. Usually when we uninstall a module, it also removes the fields, config and everything the module has installed.

    I want to uninstall a module, but I do not want it to remove anything it has installed. I want to keep everything, how can I do it?

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024