D10 compatibility

Created on 20 October 2023, about 1 year ago
Updated 15 January 2024, 10 months ago

Drupal 9 EOL is around the corner

Proposed resolution

drupal/upgrade status shows up to 7 warnings related to this module and D10 compatibility.
None of these seem too complicated to solve.

The best approach would maybe be to create a patch that fixes those, and to merge the patch into mainstream at some point.
composer lenient can be used to use this patch in the path to D10.

However, this makes sense if at some point the patch is going to be merged into mainstream.

📌 Task
Status

Needs review

Version

1.0

Component

Code

Created by

🇪🇸Spain jaims-dev

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

Comments & Activities

  • Issue created by @jaims-dev
  • First commit to issue fork.
  • @bserem opened merge request.
  • Status changed to Needs review about 1 year ago
  • 🇬🇷Greece bserem

    Please check attached patch. Also made an MR.
    This tackles the obvious differences between d9 and d10.

    Thanks

  • Open in Jenkins → Open on Drupal.org →
    Core: 10.1.x + Environment: PHP 8.1 & MariaDB 10.3.22
    last update about 1 year ago
    Composer require failure
  • 🇫🇷France paulbeaney

    Just tried applying this patch but it chokes on 2 parts relating to commerce_product_bundle.install - there are line numbers which simply don't exist in what I am seeing here, and reference $config_manager which doesn't appear anywhere in the project that I can find. Have I missed a trick? (Did a composer remove/require to ensure I had the latest version).

    Assuming I haven't, attached is a patch without the 2 offending chunks, and also including the automated patch from #3411548 to make a complete D10 update patch.

Production build 0.71.5 2024