Drupal9 is almost end of life, we need to support Drupal 10

The required access checks are added to entity queries.

The version in the info file is changed to Drupal 9 / 10

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:

Comments

jorisclaes created an issue. See original summary.

jorisclaes’s picture

While testing the Drupal 10 fork, I ran into an additional issue

Error: Call to a member function getPreferredLangcode() on bool in Drupal\commerce_stock_notifications\Plugin\QueueWorker\CommerceStockNotifyQueue->processItem() (line 114 of modules/contrib/commerce_stock_notifications/src/Plugin/QueueWorker/CommerceStockNotifyQueue.php).

I added a separate patch for this

agoradesign’s picture

Priority: Major » Critical

changed priority to critical, now that Drupal 9 is reaching EOL next month. there's not too much to do here.

I know, we all spend our spare times for maintaining our Drupal modules, but please take these few minutes and make this module D10 compatible

jcmartinez made their first commit to this issue’s fork.

jcmartinez’s picture

Code maintainers.

The MR14 adds patch #2 contributed by jorisclaes.

If you can accept the MR11 and then the MR14, we should have a version of this module compatible with D10.

Thanks!

poker10’s picture

Status: Active » Needs work

Thanks for working on this. I think we should focus on MR 11 here.

MR 14 will be solved in #3215770: anonymous cannot create notifications although /permissions allow it?, so let's not mix this up.

Added a few comments to the MR, otherwise I think this looks good.

Once we fix all outstanding issues, I will roll out a new D10 compatible release (alpha or beta).

chrisscrumping’s picture

Would be good get this merged, I am happy to help by applying the suggested changes if that's all that's required?

poker10’s picture

@ChrisScrumping yes, it would be great if you can update the MR and prepare it for review. I can take a look then a finish it / commit.

I would say we can keep old core versions and old php versions in case it does not do any harm (maybe it will be less disrupting for sites).

Thanks!

chrisscrumping’s picture

Should be okay now hopefully?

poker10’s picture

Status: Needs work » Fixed

Committed and pushed. Thanks all!

chrisscrumping’s picture

Thanks poker10 great stuff!

Status: Fixed » Closed (fixed)

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