Automatically closed - issue fixed for 2 weeks with no activity.
- 🇩🇪Germany sch4lly
Created new release 1.1 with Drupal 11 compatibility. Sorry for the delay!
- 🇬🇷Greece idimopoulos
There was an issue with the latest version of Drupal. After https://www.drupal.org/project/drupal/issues/2786355 📌 Move multiple provider plugin work from migrate into core's plugin system Active , tests that use the
entity_test
module, which has an implicit reference to the user module through the entity owner interface, will require the user module to be installed as well.
I have fixed this and the rest is working fine so I am approving this. -
idimopoulos →
committed 82823c3f on 2.x authored by
alorenc →
Issue #3431005 by alorenc: Automated Drupal 11 compatibility fixes for...
-
idimopoulos →
committed 82823c3f on 2.x authored by
alorenc →
- 🇨🇭Switzerland berdir Switzerland
">=10.1.3" is definitely wrong, that would include any future major version.
Don't care if it requires 10.3 or the helper is used, but this should be fixed, that will cause problems in the future.
requiring 10.3 would not need a new major version, even 10.3 is unsupported now and updating requirements is fine in a minor.
I was not able to test if the patch makes the module installable on D11 because I got this error:
TypeError: Drupal\user_visits\EventSubscriber\UserVisitsSubscriber::__construct(): Argument #5 ($request_stack) must be of type Drupal\Core\Http\RequestStack, Symfony\Component\HttpFoundation\RequestStack given, called in /var/www/html/web/core/lib/Drupal/Component/DependencyInjection/Container.php on line 261 in Drupal\user_visits\EventSubscriber\UserVisitsSubscriber->__construct() (line 69 of /var/www/html/repos/user_visits/src/EventSubscriber/UserVisitsSubscriber.php).
I can confirm the patch works when using the MR. (Equivalent patch would be https://git.drupalcode.org/project/block_scheduler/-/merge_requests/2/diffs.patch)
- 🇸🇮Slovenia nkoporec Slovenia
Adding a new patch that fixes a dependency issue, I have not used DI as it not posible anymore (also see the extended class in core, it also does not use DI).
- 🇺🇸United States gravelpot
@taggartj Thanks for your support to the community by maintaining this module. Would you be willing to merge this request and cut a Drupal 11-compatible release?
- 🇺🇸United States gravelpot
@larowlan @sam512 Thanks for your support of this module for the community. Would you be willing to go ahead and merge this request and cut a Drupal 11-compatible release?
- 🇺🇸United States gravelpot
Hi @andriy-khomych, this issue has been RTBC for a few months. Would you be willing to merge it and cut a D11-compatible release of this module?
Thanks for your efforts in maintaining this module for the community!
- 🇬🇧United Kingdom philipnorton42 Cheshire
Merged in these changes. Also fixed a couple of coding standards issues.
- 🇺🇸United States mark_fullmer Tucson
Noting that this change is already accounted for in the issue for Drupal 11 compatibility, per https://git.drupalcode.org/project/features/-/merge_requests/39#note_494953 . So, presumably, this issue can be closed in favor of the comprehensive changes in 📌 Drupal 11 compatibility for Features module Active
-
albeorte →
committed 38ccd77d on 4.x
Issue #3431822: Revert token for testing purposes
-
albeorte →
committed 38ccd77d on 4.x
- 🇳🇱Netherlands jeroen dost
I reguired (dev) phpstan-strict-rules in my coposer file. Removing it, reduced it to 13 problems. 10 of these were related to deprecations in this mollie module itself, which will be fixed in 3.x version. So I only patched 3 .info files to make it compatable with Drupal 11 (see attachment).
- 🇳🇱Netherlands jeroen dost
On yet another closer inspection, I had "phpstan/phpstan-strict-rules" in my composer file. I removed that and I see no problems anymore. So this should be ready for release.
- 🇳🇱Netherlands jeroen dost
Sorry, the patch did not apply. Fixed patch in attachment.
- 🇳🇱Netherlands jeroen dost
Sorry, the patch did not apply, so attached is a new patch. This also removes all instances of default_argument_skip_url in the view.
- @uroki opened merge request.
- 🇳🇱Netherlands jeroen dost
It loks like only a type hint is in this patch. Drupal Upgrade Status module reports more problems.
Attached a patch to remove all problems reported by upgrade status. - First commit to issue fork.
- 🇳🇱Netherlands jeroen dost
This removed problems reported by Upgrade status and marks it Drupal 11 ready. I think it is indeed ready for a D11 release.
- 🇬🇷Greece idimopoulos
idimopoulos → made their first commit to this issue’s fork.
- 🇳🇱Netherlands jeroen dost
I applied the patch on my Drupal 10 site and it reduced the reported messages from the upgrade status scan from 56 to 34.
In the attached file (upgrade-status-export-2025-08-05.txt) are the remaining problems. Do I need to create a new issue for these reported problems that cannot be fixed bij Drupal Rector? Or is this the place to collect all D11 issues? - @plopesc opened merge request.
- 🇦🇺Australia thomwilhelm Sydney
Hey @schiavone looking at this module for Drupal 11, I can't see an MR that has made this Drupal 11 compatible yet.
https://git.drupalcode.org/project/tealiumiq/-/tree/8.x-1.x
https://git.drupalcode.org/project/tealiumiq/-/blob/8.x-1.x/tealiumiq.in...If I can help at all let me know. Would be great to see a Drupal 11 compatible release for this module!
- 🇮🇳India vinodhini.e chennai
Hi, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !18, the module is now compatible with Drupal 11. Thanks. -
realityloop →
committed 597f0337 on 1.2.x authored by
jradhak →
Issue #3429976 by realityloop, jradhak: Automated Drupal 11...
-
realityloop →
committed 597f0337 on 1.2.x authored by
jradhak →
- 🇦🇺Australia realityloop
we shouldn't remove support for earlier versions of Drupal unless there are breaking changes
- First commit to issue fork.
-
czigor →
committed 32df249f on 2.0.x authored by
project update bot →
Issue #3451114 by czigor, siegrist: Automated Drupal 11 compatibility...
-
czigor →
committed 32df249f on 2.0.x authored by
project update bot →
-
bradjones1 →
committed 671abf15 on 1.0.x
Issue #3440793 by project update bot, bradjones1: Automated Drupal 11...
-
bradjones1 →
committed 671abf15 on 1.0.x
- First commit to issue fork.
- @bradjones1 opened merge request.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇨🇦Canada m4olivei Grimsby, ON
The 3.0.x version no longer requires fakeobjects. There is also another D11 update issue that is filed against the 3.0.x branch, which is more than likely the place where D11 support will be added.
Closing as duplicate of 📌 Automated Drupal 11 compatibility fixes for ckeditor_drupalbreaks Needs review .
-
heddn →
committed 021234dd on 8.x-1.x authored by
jeremy1606 →
Issue #3451232 by jeremy1606, heddn: Automated Drupal 11 compatibility...
-
heddn →
committed 021234dd on 8.x-1.x authored by
jeremy1606 →
-
heddn →
committed 070af3ed on 1.0.x authored by
project update bot →
Issue #3430537 by jeremy1606, heddn: Automated Drupal 11 compatibility...
-
heddn →
committed 070af3ed on 1.0.x authored by
project update bot →
- First commit to issue fork.
- 🇺🇸United States euk
@sprocketman In general... if you are using a patch form the MR there could be issues due to differences in the targets: MR9 is issued against the dev version, you might be trying to apply it against a release.
I am attaching a patch that worked for me back when I created the MR9.
Automatically closed - issue fixed for 2 weeks with no activity.
- Issue created by @parkhillrecords
- 🇬🇧United Kingdom d.fisher
Hey Rajas. Changes look good on first glance. I've opened a merge request:
https://git.drupalcode.org/issue/file_browser-3451080/-/merge_requests/1/Daniel and I will review and merge if we can (we should have permission to do so). Then we aim to fix the tests which seem to have broken again and hopefully by that time I will have become a maintainer and we can roll this out to a stable release.
- 🇮🇳India vinodhini.e chennai
Hi, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !7, the module is now compatible with Drupal 11. Thanks. -
stefanos.petrakis →
committed 59d531bb on 3.x
Issue #3430966 by stefanos.petrakis, jeroent, alt.dev: Automated Drupal...
-
stefanos.petrakis →
committed 59d531bb on 3.x
- 🇨🇭Switzerland stefanos.petrakis@gmail.com Biel, Switzerland
This one is ready to go in; re-enabled the icalvalidator service for gitlab-ci
PR 17 and 21 taken into account and no longer needed. -
idimopoulos →
committed b16d695e on 1.x authored by
saidatom →
Issue #3451198 by saidatom: Automated Drupal 11 compatibility fixes for...
-
idimopoulos →
committed b16d695e on 1.x authored by
saidatom →
- 🇬🇷Greece idimopoulos
idimopoulos → made their first commit to this issue’s fork.
- @saidatom opened merge request.
- First commit to issue fork.
- @alorenc opened merge request.
- 🇵🇱Poland alorenc Wolsztyn, 🇵🇱
First, we need to commit #3396336 as it fixes pipeline issues
Is there any possibility to get the D11 version instead of applying the patches and changing the core_version_requiremen or making changes in the composer.json file?
- @stefanospetrakis opened merge request.
- 🇨🇭Switzerland stefanos.petrakis@gmail.com Biel, Switzerland
stefanos.petrakis → made their first commit to this issue’s fork.
- 🇺🇸United States karolus
Interesting comments on the original summary. Wasn't thinking of the way non-English speakers would interpret the term drop. Hope the edits are understandable.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇨🇦Canada Charlie ChX Negyesi 🍁Canada
The easy way to use an issue fork is to use the chx/drupal-issue-fork composer plugin.
-
eiriksm →
committed 39ce63be on 8.x-1.x authored by
project update bot →
Issue #3428457 by project update bot, eiriksm: Automated Drupal 11...
-
eiriksm →
committed 39ce63be on 8.x-1.x authored by
project update bot →
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇹Italy aronne
Hi all,
I’m gonna update it in few minutes.
New release for Drupal 11 coming soon. - 🇮🇳India rajas samse
Hello,
I have updated the README.txt file to align with modern standards and workflows for Drupal 11.
The changes are available on the "my-doc-updates" branch in the issue fork for review.
Could a contributor for MR !6 (like @d.fisher or @daniel.j) please merge this branch into the main 3451080-automated-drupal-11 branch?Thank you!
- 🇮🇳India rajas samse
rajas samse → made their first commit to this issue’s fork.
- 🇦🇺Australia VladimirAus Brisbane, Australia
vladimiraus → changed the visibility of the branch project-update-bot-only to hidden.
- @vladimiraus opened merge request.
- First commit to issue fork.
- 🇮🇳India mohit_aghera Rajkot
Created a new release.
https://www.drupal.org/project/redirect_metrics/releases/2.0.3 →Thanks everyone!
Please let me know if you come across any other issues.
Happy to fix those. - 🇮🇳India mohit_aghera Rajkot
Closing this in favour of 📌 Automated Drupal 11 compatibility fixes for redirect_metrics Needs review
New release 2.0.3 should be available today. - 🇮🇳India mohit_aghera Rajkot
Closing this in favour of 📌 Automated Drupal 11 compatibility fixes for redirect_metrics Needs review
- 🇮🇳India mohit_aghera Rajkot
I did a quick test on local, looks good.
I've merged the PR and will cut the new release. - 🇺🇸United States bradjones1 Digital Nomad Life
The issue in #33 is, AFAICT, actually a regression in Flysystem relating to image style generation with non-local/remote adapters. So this was early smoke from that regression. See 🐛 Image style generation no longer works for non-local drivers in Active .
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
-
afeijo →
committed d75ded77 on 2.x authored by
project update bot →
Issue #3433770 by project update bot: Automated Drupal 11 compatibility...
-
afeijo →
committed d75ded77 on 2.x authored by
project update bot →
- @alorenc opened merge request.
- First commit to issue fork.
- 🇸🇮Slovenia deaom
Removed support for D9 and updated tests in preparation for D11. Marking the issue as needs work, so there is no confusion. MR is set to draft as work is still ongoing.
- 🇮🇳India vinodhini.e chennai
I have installed this module on Drupal 11.2.2.
I ran the Upgrade Status report and found two issues.
I have fixed both issues, and the module is now compatible with Drupal 11. Thanks. - @vinodhinie opened merge request.
- 🇮🇳India vinodhini.e chennai
vinodhini.e → made their first commit to this issue’s fork.
Automatically closed - issue fixed for 2 weeks with no activity.
- @deaom opened merge request.
- First commit to issue fork.
- Issue created by @rzb
- @neerajsingh opened merge request.
- 🇵🇱Poland alorenc Wolsztyn, 🇵🇱
Moved to “Needs Work” because the current state generates a fatal error.
- 🇵🇱Poland alorenc Wolsztyn, 🇵🇱
I have performed some tests, and it generates a fatal error on both versions of private_messages (v3 and v4).
private_message v4
Fatal error: Declaration of Drupal\private_message_flood\Plugin\PrivateMessageConfigForm\PrivateMessageFloodPrivateMessageConfigForm::create(Symfony\Component\DependencyInjection\ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition) must be compatible with Drupal\private_message\Plugin\PrivateMessageConfigForm\PrivateMessageConfigFormBase::create(Symfony\Component\DependencyInjection\ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition):private_message v3
Fatal error: Declaration of Drupal\private_message_flood\Plugin\PrivateMessageConfigForm\PrivateMessageFloodPrivateMessageConfigForm::validateForm(array &$form, Drupal\Core\Form\FormStateInterface $formState) must be compatible with Drupal\private_message\Plugin\PrivateMessageConfigForm\PrivateMessageConfigFormBase::validateForm(array &$form, Drupal\Core\Form\FormStateInterface $formState): void in /var/www/html/web/modules/repos/private_message_flood/src/Plugin/PrivateMessageConfigForm/PrivateMessageFloodPrivateMessageConfigForm.php on line 200In both cases we have
Error: Call to undefined function Drupal\private_message_flood\Plugin\PrivateMessageConfigForm\user_role_names() in Drupal\private_message_flood\Plugin\PrivateMessageConfigForm\PrivateMessageFloodPrivateMessageConfigForm->buildForm() (line 81 of modules/repos/private_message_flood/src/Plugin/PrivateMessageConfigForm/PrivateMessageFloodPrivateMessageConfigForm.php).
which makes sense as user_role_names is no longer aviable in D11First, we need to resolve/merge https://www.drupal.org/project/private_message_flood/issues/3501011 📌 Private message 4 compatibility fixes Active and issues should disappear.
- 🇮🇳India vinodhini.e chennai
Hello @milant, I tested the module using Patch #5 on Drupal 11. However, I'm encountering the following fatal error when trying to install the module:
TypeError: Drupal\saml_rules\EventSubscriber\SAMLRulesAnonymousLogin::checkAuthStatus(): Argument #1 ($event) must be of type Symfony\Component\HttpKernel\Event\GetResponseEvent, Symfony\Component\HttpKernel\Event\RequestEvent given, called in /var/www/html/vendor/symfony/event-dispatcher/EventDispatcher.php on line 246 in Drupal\saml_rules\EventSubscriber\SAMLRulesAnonymousLogin->checkAuthStatus() (line 24 of modules/contrib/saml_rules-3434309/src/EventSubscriber/SAMLRulesAnonymousLogin.php).
- 🇮🇳India pandurengan.jegadeesan
When can we expect this issue to be fixed into a proper release to support Drupal 11 compatibility?
- 🇮🇳India pandurengan.jegadeesan
When can we expect this issue to be fixed into a proper release to support Drupal 11 compatibility?
- 🇮🇳India pandurengan.jegadeesan
When can we expect this issue to be fixed into a proper release to support Drupal 11 compatibility?
- 🇮🇳India pandurengan.jegadeesan
When can we expect this issue to be fixed into a proper release?
- 🇮🇳India vinodhini.e chennai
Hi, @zhelmet , Could you please provide it as a merge request?
- 🇳🇿New Zealand Gold 20 minutes in the future
I have to agree with @rachel_norfolk. Dropping ^8.8 shouldn't be done in this ticket.
The MR at merge request !27 is the one to go with.
- 🇺🇸United States MilanT
Hello all,
This patch updates saml_rules.info.yml to allow Drupal 11, and replaces the removed user_role_names() call with a Role::loadMultiple() loop in
SAMLRulesAuthenticationRuleForm.Also included is the Rector patch from the project update bot.
I also was not able to apply the "allowed_options.2.0.0.rector.patch" patch, but I WAS able to apply the "allowed_options_d11_version_fix_3428840_4.patch.patch" to install the module on D11.
- 🇳🇮Nicaragua jeremy1606
Of course, I have also tested the module and can guarantee that it works, so: +1 RTBC
- 🇳🇮Nicaragua jeremy1606
I added a cspell-project-words.txt file to avoid the only error that cspell flagged in the GitLab pipelines, since, upon searching for the error, it was a word that could not be changed within README.md. The composer.json has also been changed from 2.x to avoid the validation error in the composer-lint test.
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
- @bluegeek9 opened merge request.
- 🇮🇳India vinodhini.e chennai
Hi, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !4, the module is now compatible with Drupal 11. Thanks. - 🇮🇳India vinodhini.e chennai
Hi @akashkumar07,
I've updated the constructor parameter details and verified the code with PHPCS — no warnings or errors were reported.
Please review and let me know if anything else needs to be addressed.
Thanks.. Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India AkashKumar07
Hi @Vinodhini
There are couple of small changes required related to coding standard in the MR.
Thanks! - First commit to issue fork.
- 🇮🇳India vinodhini.e chennai
Hi, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !3, the module is now compatible with Drupal 11. Thanks. - 🇫🇷France Renrhaf 📍 Strasbourg 🐦🦜
A new D11 compatible release would be great ! thanks !
- 🇺🇸United States sprocketman
MR9 didn't work for me due to additional spaces before lines 78-80.
- 🇳🇮Nicaragua jeremy1606
I have added a commit where I add compatibility with D11 in the submodules of the main module by editing their .info.yml files. I welcome any suggestions or comments.