Drupal 10 Compatibility for 2.x

Created on 27 May 2024, 4 months ago
Updated 7 June 2024, 4 months ago

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

šŸ“Œ Task
Status

Needs review

Version

2.0

Component

Code

Created by

šŸ‡µšŸ‡ŖPeru krystalcode

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

Comments & Activities

  • Issue created by @krystalcode
  • Status changed to Needs review 4 months ago
  • šŸ‡µšŸ‡ŖPeru krystalcode

    Made installable on Drupal 10. No code changes seem to be required, but I will this issue after testing on Drupal 10 is done.

  • šŸ‡µšŸ‡­Philippines cleavinjosh

    Hi @krystalcode,

    I am not sure if this is what you meant but I got an error while trying to install 2.x-dev via composer.

    āžœ  drupal-org-issues git:(main) āœ— composer require 'drupal/commerceg:2.x-dev@dev'
    ./composer.json has been updated
    Running composer update drupal/commerceg
    Loading composer repositories with package information
    Updating dependencies
    Your requirements could not be resolved to an installable set of packages.
    
      Problem 1
        - drupal/commerce[2.17.0, ..., 2.18.0] require drupal/core ^8.7.7 || ^9 -> found drupal/core[8.7.7, ..., 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/commerce[2.19.0, ..., 2.24.0] require drupal/core ^8.8 || ^9 -> found drupal/core[8.8.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/commerce[2.25.0, ..., 2.28.0] require drupal/core ^8.9 || ^9 -> found drupal/core[8.9.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/commerce[2.29.0, ..., 2.36.0] require drupal/inline_entity_form ^1.0@RC -> found drupal/inline_entity_form[dev-1.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x)] but it does not match your minimum-stability.
        - drupal/commerce[2.37.0, ..., 2.39.0] require drupal/inline_entity_form ^1.0@RC || ^3.0@RC -> found drupal/inline_entity_form[dev-1.x, dev-3.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x), 3.0.0-rc15, ..., 3.x-dev (alias of dev-3.x)] but it does not match your minimum-stability.
        - drupal/commerceg 2.x-dev is an alias of drupal/commerceg dev-2.x and thus requires it to be installed too.
        - drupal/commerceg dev-2.x requires drupal/commerce ^2.17 -> satisfiable by drupal/commerce[2.17.0, ..., 2.39.0].
        - Root composer.json requires drupal/commerceg 2.x-dev@dev -> satisfiable by drupal/commerceg[2.x-dev (alias of dev-2.x)].
    
    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.
    āžœ  drupal-org-issues git:(main) āœ—

    I am using Drupal 10.1.8.

    Please advise.
    Thank you.

  • šŸ‡µšŸ‡ŖPeru krystalcode

    Doesn't seem an issue with this module, looks like the inline_entity_form module cannot be installed because it does not have a stable release and you only accept stable modules. Try adding the following to your project's composer.json:

    "minimum-stability": "dev",
    "prefer-stable": true,
    

    Then composer require drupal/commerceg

  • šŸ‡µšŸ‡­Philippines cleavinjosh

    Hi @krystalcode,

    I followed your advise and now I successfully downloaded both 2.x-dev via composer require 'drupal/commerceg:2.x-dev@dev'

    āžœ  drupal-org-issues git:(main) āœ— composer require 'drupal/commerceg:2.x-dev@dev'
    ./composer.json has been updated
    Running composer update drupal/commerceg
    Loading composer repositories with package information
    Updating dependencies
    Lock file operations: 0 installs, 1 update, 0 removals
      - Upgrading drupal/commerceg (2.0.0-alpha2 => dev-2.x 53b6534)
    Writing lock file
    Installing dependencies from lock file (including require-dev)
    Package operations: 2 installs, 0 updates, 0 removals
      - Syncing drupal/commerceg (dev-2.x 53b6534) into cache
      - Installing drupal/commerce (2.39.0): Extracting archive
      - Installing drupal/commerceg (dev-2.x 53b6534): Cloning 53b6534288 from cache
    Generating autoload files
    48 packages you are using are looking for funding.
    Use the `composer fund` command to find out more!
    No security vulnerability advisories found.
    āžœ  drupal-org-issues git:(main) āœ—

    and

    2.0.0-alpha2 via composer require drupal/commerceg.

    āžœ  drupal-org-issues git:(main) āœ— composer require drupal/commerceg
    ./composer.json has been updated
    Running composer update drupal/commerceg
    Loading composer repositories with package information
    Updating dependencies
    Lock file operations: 12 installs, 0 updates, 0 removals
      - Locking commerceguys/addressing (v2.2.0)
      - Locking commerceguys/intl (v2.0.5)
      - Locking doctrine/collections (2.2.2)
      - Locking drupal/address (2.0.1)
      - Locking drupal/commerce (2.39.0)
      - Locking drupal/commerceg (2.0.0-alpha2)
      - Locking drupal/flexible_permissions (1.1.0)
      - Locking drupal/group (3.2.2)
      - Locking drupal/inline_entity_form (3.0.0-rc19)
      - Locking drupal/profile (1.10.0)
      - Locking drupal/state_machine (1.11.0)
      - Locking drupal/variationcache (1.5.0)
    Writing lock file
    Installing dependencies from lock file (including require-dev)
    Package operations: 12 installs, 0 updates, 0 removals
      - Downloading commerceguys/intl (v2.0.5)
      - Downloading doctrine/collections (2.2.2)
      - Downloading commerceguys/addressing (v2.2.0)
      - Downloading drupal/address (2.0.1)
      - Downloading drupal/group (3.2.2)
      - Downloading drupal/state_machine (1.11.0)
      - Downloading drupal/profile (1.10.0)
      - Downloading drupal/inline_entity_form (3.0.0-rc19)
      - Downloading drupal/commerce (2.39.0)
      - Downloading drupal/commerceg (2.0.0-alpha2)
      - Installing commerceguys/intl (v2.0.5): Extracting archive
      - Installing doctrine/collections (2.2.2): Extracting archive
      - Installing commerceguys/addressing (v2.2.0): Extracting archive
      - Installing drupal/address (2.0.1): Extracting archive
      - Installing drupal/variationcache (1.5.0): Extracting archive
      - Installing drupal/flexible_permissions (1.1.0): Extracting archive
      - Installing drupal/group (3.2.2): Extracting archive
      - Installing drupal/state_machine (1.11.0): Extracting archive
      - Installing drupal/profile (1.10.0): Extracting archive
      - Installing drupal/inline_entity_form (3.0.0-rc19): Extracting archive
      - Installing drupal/commerce (2.39.0): Extracting archive
      - Installing drupal/commerceg (2.0.0-alpha2): Extracting archive
    1 package suggestions were added by new dependencies, use `composer suggest` to see details.
    Generating autoload files
    48 packages you are using are looking for funding.
    Use the `composer fund` command to find out more!
    No security vulnerability advisories found.
    Using version ^2.0@alpha for drupal/commerceg
    āžœ  drupal-org-issues git:(main) āœ—

    How would you like me to proceed?

    Please advise.
    Thank you.

  • šŸ‡µšŸ‡ŖPeru krystalcode

    In general it is better to use releases i.e. 2.0.0-alpha2 rather than the main development branch, unless you are planning to contribute code to this module.

Production build 0.71.5 2024