🇮🇳India @vipin.mittal18

Hello Martin,

It would be greatly appreciated if you could find some time to release a Drupal 11 compatible version of simple_gmap so that the community can upgrade to the most recent version of Drupal. Thanks!

Hello @dave,

It would be greatly appreciated if you could find some time to release a Drupal 11 compatible version of embed so that the community can upgrade to the most recent version of Drupal. Thanks!

MR !24 is working fine on Drupal 11.

Duplicate of 📌 Add Gitlab CI Fixed

Hello @rajeshreeputra, Would you like to elaborate the issue a bit more?

vipin.mittal18 → changed the visibility of the branch 3485873-dependency-injection-anti-patterns to hidden.

vipin.mittal18 → created an issue. See original summary → .

gotcha. Thanks very much Damien for your prompt confirmation!

According to my perspective, it does not make sense to make Panelizer compatible with Drupal 11, since maintainers have already announced no further development and provided upgrade paths to Layout builder. Maintainers are also not supporting D11 compatibility in 4.x version 📌 Drupal 11 compatibility fixes for panelizer [v4] Active .

@damienmckenna, Could you please let us know if you intend to make D11 compatible and see any values?

Thanks @sdjili for your response!

Hello @hchonov,

I hope you’re doing well! I’m reaching out to ask about the release plans for this module with Drupal 11 compatibility. Any updates on the timeline would be greatly appreciated. Thanks!

Hello @martin107,

I hope you’re doing well! I’m reaching out to ask about the release plans for this module with Drupal 11 compatibility. Any updates on the timeline would be greatly appreciated. Thanks!

One can use composer require 'drupal/jwt:3.x-dev' to download the JWT D11 compatible version.

To avoid any breakable changes in dev version, one can use composer require 'drupal/jwt:3.x-dev#5fe746dc'

Drupal starter kit Place support latest drupal versions.

This module supports latest Drupal version.

https://www.drupal.org/project/acquia_cms_person/releases/1.5.2 →

D10 has been supported from version https://www.drupal.org/project/acquia_cms_tour/releases/2.1.4 →

D10 has been supported from version https://www.drupal.org/project/acquia_cms_tour/releases/1.3.5 →

Drupal 1o version has been supported from version https://www.drupal.org/project/acquia_cms_video/releases/1.5.1 →

D11 stable version has been released. Refer https://www.drupal.org/project/acquia_cms_video/releases/1.6.2 →

D11 stable version has been released. Refer https://www.drupal.org/project/acquia_cms_tour/releases/2.1.13 →

D11 stable version has been released. Refer https://www.drupal.org/project/acquia_cms_site_studio/releases/1.6.4 →

D11 stable version has been released. Refer https://www.drupal.org/project/acquia_cms_place/releases/1.6.4 →

D11 stable version has been released. Refer https://www.drupal.org/project/acquia_cms_page/releases/1.6.1 →

D11 compatible version has been released. Refer https://www.drupal.org/project/acquia_cms_component/releases/1.3.12 →

D11 stable version has been released. Refer https://www.drupal.org/project/acquia_cms_search/releases/1.6.2 →

Hello @sdjili,

There is no constraint which prevents this module from upgrading to the latest 2.x version of drupal/facets. Refer https://git.drupalcode.org/project/acquia_cms_search/-/blob/1.6.2/compos...

I have tried on the Drupal 10 and Drupal 11 versions to upgrade the Acquia CMS Search module and have been able to do so. Refer attached screenshots

Kindly refer the page to resolve the issue that you are experiencing.

vipin.mittal18 → made their first commit to this issue’s fork.

vipin.mittal18 → created an issue.

Released https://www.drupal.org/project/media_entity_download_count/releases/1.0.1 →

I am not able to replicate the issue. Kindly provide the steps to reproduce the issue.

I am not able to replicate the issue. Kindly provide the specific steps.

Thanks for brining up. I will do the release ASAP.

Hello @pwolanin,

I wanted to ask if there are any plans or possibilities for releasing a Drupal 11 compatible version of the jwt module. Thanks!

vipin.mittal18 → created an issue.

vipin.mittal18 → made their first commit to this issue’s fork.

vipin.mittal18 → created an issue.

The fix has been functioning perfectly on my side.

Thank you very much, Samuel, for releasing the stable Drupal 11 version. This indicates that you're still actively maintaining the module. Please let us know if you're still interested in having co-maintainers for this project; otherwise, kindly close this request.

I believe the drupal/acquia_telemetry-acquia_telemetry conflict in the composer file can be removed as it is no longer relevant

@bohart, Can we get a stable release of the reroute email module 2.2.x now that all requirements for Drupal 11 readiness have been addressed?

@bohart: I also believe that including a composer.json file in your Drupal module can still offer several benefits, even though it might be generated or handled by tools like drupal-org packagist.

Hello @bircher,

I hope you had a fantastic break! Just checking in to see if you’re back and available to do stable release. Thanks!

Hello @svenryen,

I hope you had a wonderful vacation! Just checking in to see if you’re back and available to do stable release. Thanks!

I could not agree more with @vishalkhode more as coding standards issues should not be included in Drupal11 compatibility fixes. It should be fixed at separate ticket which I can see already created at https://www.drupal.org/project/config_update/issues/3465396 📌 Fix validate pipeline Needs review .

In order to prevent duplicate tickets, I have added a project bot.

Hello Neslee, I would appreciate it if you could release a stable version of Drupal 11 compatible version, as we are dependent on it for releasing our code. Thanks!

Duplicate of https://www.drupal.org/project/social_media_links/issues/3449085 📌 Automated Drupal 11 compatibility fixes RTBC and a full set of fixes and verifications has also been completed.

Hello @berdir,

I am completely agree with you that it takes time to release stable releases by covering all the corner cases with all the different issues logged. Please accept my sincere apologies if it hurts by my followup, but my intention is to learn the timeline of this module so that Acquia CMS Common → module can be planned accordingly. I will ensure you do not receive further followups on any other tickets and apologize again if I upset you in any way. Thanks for the stable release too and unblocking us.

Thanks very much Lee.

Hello @Berdir,

Given that Drupal 11 is nearing its release, will we see a stable version of this module beforehand? Thanks!

Hello @Berdir,

With Drupal 11's release coming up, can we anticipate a stable version of this module before then? Thanks!

Hello @nils.destoop,

We are approaching the release of Drupal 11, so should we expect stable version for this module before that release? Thanks!

Hello @Berdir,

We are approaching the release of Drupal 11, so should we expect stable version for this module before that release? Thanks!

Hello Lee,

There is something a little confusing about the release version 1.2.2 since a new release(1.2.6) should support Drupal 11 and I cannot find any such release. Would you please take a look again.

Hello @WalkingDexter,

We are approaching the release of Drupal 11, so should we expect stable version for this module before that release? Thanks!

Hello @pwolanin,

We are approaching the release of Drupal 11, so should we expect stable version for this module before that release? Thanks!

It appears that all issues mentioned at #35 are marked "RTBC" with all test cases passing and then MR !57 can be merged.

Hello Christian,

We are approaching the release of Drupal 11, so should we expect this module to be compatible with Drupal 11? Thanks!

Hello @Mateu,

We are approaching the release of Drupal 11 and consumers → now have D11 stable version, so should we expect this module to be compatible with Drupal 11? Thanks!

Hello Giuseppe87,
The module does not intend to redirect the user to an external site. However, I am interested in hearing more about the case scenario if it occurs in the real world.

Duplicate of https://www.drupal.org/project/popular_search_keywords/issues/3297880 📌 Automated Drupal 10 compatibility fixes RTBC as I see maintainer is also working on that issue.

In order to support multiple roles for the user, numerous changes have been made in the code that resolve this issue and it is no longer necessary to apply these code fixes.

Hello @TR,

We are approaching the release of Drupal 11, so should we expect this module to be compatible with Drupal 11? Thanks!

Hello @Nick & @Matt,

We are approaching the release of Drupal 11, so should we expect this module to be compatible with Drupal 11? Thanks!

Hello Joël & Samuel,

Would it be possible to release a Drupal 11 compatible version before the Drupal 11 stable version is released next week?

Thanks!

Fixes are working perfectly on Drupal version 11.0.0-rc1. Refer below screenshot

Hello Kristen,

How are you doing?

Despite my best efforts, I was unable to reproduce the issue again, even after a fresh installation with Drupal 11.0.0-rc1. This issue appears not to exist, as my colleagues also tried to replicate it. Therefore, I believe we can release a Drupal 11 compatible stable version of password policy. Apologies for any disruption.

An animated GIF is created as a reference to indicate that there are no more warnings being logged

There is warnings

Warning: Undefined array key "character_length" in Drupal\password_policy_length\Plugin\PasswordConstraint\PasswordLength->validateConfigurationForm() (line 130 of /home/ide/project/docroot/modules/contrib/password_policy/password_policy_length/src/Plugin/PasswordConstraint/PasswordLength.php)

on saving "character length" password constraint but can be ignored for this ticket as restriction works perfectly.

vipin.mittal18 → changed the visibility of the branch 3433859-automated-drupal-11 to active.

vipin.mittal18 → changed the visibility of the branch 3433859-automated-drupal-11 to hidden.

Hello @adriancid @eme @fethi.krout @matio89 @Emerya.thomas,

Please accept my apologies for bothering you, but I would appreciate it if you could release a Drupal 11 compatible version as we have put in a great deal of effort to fix the compatibility issues. If you are no longer maintaining this, please add me as a maintainer, so we can provide support for Drupal 11 customers that will be very helpful in the long run.

Thanks!

Hello Samuel & Joël,

Please accept my apologies for bothering you, but I would appreciate it if you could release a Drupal 11 compatible version as we have put in a great deal of effort to fix the compatibility issues. If you are no longer maintaining this, please add me as a maintainer, so we can provide support for Drupal 11 customers that will be very helpful in the long run.

Thanks!

Hello Jonathan,

Please accept my apologies for bothering you, but I would appreciate it if you could release a Drupal 11 compatible version as we have put in a great deal of effort to fix the compatibility issues. If you are no longer maintaining this, please add me as a maintainer, so we can provide support for Drupal 11 customers that will be very helpful in the long run.

Thanks!

Hello Christian,

Please accept my apologies for bothering you, but I would appreciate it if you could release a Drupal 11 compatible version as we have put in a great deal of effort to fix the compatibility issues. If you are no longer maintaining this, please add me as a maintainer, so we can provide support for Drupal 11 customers that will be very helpful in the long run.

Thanks!

Hello @Nick & @Matt,

Please accept my apologies for bothering you, but I would appreciate it if you could release a Drupal 11 compatible version as we have put in a great deal of effort to fix the compatibility issues. If you are no longer maintaining this, please add me as a maintainer, so we can provide support for Drupal 11 customers that will be very helpful in the long run.

Thanks!

Hello @Mateu,

Please accept my apologies for bothering you, but I would appreciate it if you could release a Drupal 11 compatible version as we have put in a great deal of effort to fix the compatibility issues. If you are no longer maintaining this, please add me as a maintainer, so we can provide support for Drupal 11 customers that will be very helpful in the long run.

Thanks!

Hello eojthebrave,

You should keep the current naming and go with 8.x-1.18 even if you drop support for Drupal 8. The changes also meet the criteria of a patch version that fixes issues without introducing new functionality.

It would be helpful if you could inform when you intend to release a pre/stable version of consumers as Drupal 11 stable is nearing its release date. Thanks!

This ticket is duplicate of https://www.drupal.org/project/consumers/issues/3429497 📌 Automated Drupal 11 compatibility fixes for consumers RTBC

The bot has been reinstated in order to prevent multiple tickets( https://www.drupal.org/project/consumers/issues/3459583 📌 Automated Drupal 11 compatibility fixes for consumers Needs review ) from being opened simultaneously.

Hello Berdir,

Thanks very much for development release of default_content module that help us to validate our module acquia_cms_starter → depend on this module. It would be appreciated if you could let us know your timeline for releasing a pre/stable version of the default_content, especially since Drupal 11 stable is nearing its release date

Hello Berdir,

Thanks very much for development release of entity_reference_revisions module that help us to validate our module depend on this module. It would be appreciated if you could let us know your timeline for releasing a pre/stable version of the entity_reference_revisions, especially since Drupal 11 stable is nearing its release date.

Thanks!

Hello David,

Thanks for development release of token module, It would be helpful if you could inform when you intend to release a pre/stable version of honeypot as Drupal 11 stable is nearing its release date. Thanks!