Add Drupal 11.0 Support

Created on 2 September 2024, 7 months ago

Problem/Motivation

D11 has been released, we need to add D11 support.

Normally we should start at the top and work back, however as 3.x is our only supported release we will update 3.x first and port up.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

3.0

Component

Code

Created by

🇺🇸United States cmlara

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

Merge Requests

Comments & Activities

  • Issue created by @cmlara
  • Status changed to Needs review 7 months ago
  • 🇮🇳India Rajan Kumar@2026

    Hello

    I have tested MR!58 in the local environment using the Drupal Upgrade Status module. RabbitMQ modules are now supported in Drupal 11.0. Attached is a screenshot for reference. Thank you!

  • 🇵🇱Poland marcin maruszewski

    Is there any chance of a D11 compatible release? Related MR looks good and works for my Drupal test instance.

  • 🇳🇴Norway steinmb

    The module looks a little dead. We moved away from it and simply just used php-amqplib/php-amqplib directly in a custom module. We needed custom code anyway.

  • 🇺🇸United States cmlara

    This project is in a bit of a weird spot right now.

    I was added as a maintainer through the accelerated adoption process some time back.

    That process (along with the entire D.O. adoption process) is subject to some rather significant ethic questions as it is essentially a social engineering and supply chain attack.

    Factor in that one maintainers returned for a short period of time last yesr (before disappearing again) raising questions with some of my design choices and it raises even more ethical questions about my right to commit code to the project.

    The project has been heavily on hold since those incidents.

    I’ve been pondering my options, at the moment the following two look to be the most likely paths:

    1. Owner transfers the project of their own free will (do not use the Project Ownershop Queue) (may not happen due to non responsive maintainer)
    2. Fork into a new project.

    It’s a situation that needs to be sorted out for this project to be able to continue on.

    Side note:
    I’ll note no one has actually tested the code above and reported back.
    The user rajan kumar@2026 is well known for not testing code/credit farming leading to disciplinary action on D.O.

  • 🇵🇱Poland marcin maruszewski

    > The module looks a little dead.
    @steinmb, "1,953 sites report using this module".

    > The project has been heavily on hold since those incidents.

    Does it mean that we can't merge https://git.drupalcode.org/project/rabbitmq/-/merge_requests/58 ? These changes are quite straightforward and allow the module to work in Drupal 11 as well.

  • 🇺🇸United States cmlara

    Does it mean that we can't merge https://git.drupalcode.org/project/rabbitmq/-/merge_requests/58 ? These changes are quite straightforward and allow the module to work in Drupal 11 as well.

    It means that at this time I do not feel comfortable merging any more commits into the repository without a clear approval from maintainers added through a less ethically questionable process.

    I've reached out to the current owner (who was seen active a few days ago) and have started looking at the fork process as an option if needed.

Production build 0.71.5 2024