#ProjectUpdateBotD11

+1

I can confirm the patch in #4 can be applied and allows the installation of the module on D11.

However, I was presented with this error on the login page:

Deprecated function: explode(): Passing null to parameter #2 ($string) of type string is deprecated in nofollow_noindex_page_attachments() (line 22 of /var/www/html/repos/nofollow_noindex/nofollow_noindex.module).

This did not stop the site from working; I was able to edit and save the module configuration without issue and the error then did not appear again.

chris dart → made their first commit to this issue’s fork.

I have put everything from this issue that is not related to Drupal 11 compatibility into 📌 Add composer.json Active . Tests are passing there. Merge that first and this issue becomes only about Drupal 11.

I'm OK with everything @berdir said.

Personally I prefer not mixing in coding standard and spelling fixes in a compatibility issue, it just makes it much larger and those aren't necessary to have a green MR. But it's done, so leaving that to a maintainer to decide.

I'd also completely remove the composer.json, it doesn't add any value, that will be overwritten anyway on drupal.org and the description is outdated, this isn't a core theme anymore. But that too is a maintainer decision.

Tests are now passing. The problem was the repositories key in composer.json. The tests also needed an update.

Tests are failing pretty hard due to the composer.json. I don't think that's required, defining repositories like that is not valid in a module/theme and there are no dependencies except core. Lets remove that?

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

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

thtas → closed merge request !3

Is anyone working on this for Drupal 11?

Since the common practice is to create a new branch when we drop compatibility for major versions of Drupal,
I am pretty sure that defining core version as >=10 is not a good idea,
as we also know that this module will become incompatible with either Drupal 12 or Drupal 13, when the hook system is deprecated for example.

So it is better to define the compatibility the normal way
core_version_requirement: ^10 || ^11

voleger → closed merge request !47

voleger → closed merge request !41

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

Created new release 1.1 with Drupal 11 compatibility. Sorry for the delay!

Please provide a new release!

Fixed in 1.0.5 release. Thanks for gold for input.

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.

">=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)

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).

@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?

@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?

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!

Thanks!

Released in 1.0.1.

Merged in these changes. Also fixed a couple of coding standards issues.

Hi there,

Here is the updated patch for D11.

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

MR !3 has been merged and the new version 4.1.0, compatible with Drupal 11, has been released.

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).

uroki → closed merge request !14

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.

Sorry, the patch did not apply. Fixed patch in attachment.

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.

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.

This removed problems reported by Upgrade status and marks it Drupal 11 ready. I think it is indeed ready for a D11 release.

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

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?

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!

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.

we shouldn't remove support for earlier versions of Drupal unless there are breaking changes

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

Added a new patch that also fixes the logger issue

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 .

Thanks for the contributions.

Thanks for these contributions.

@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.

Changes seems correct to me

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.

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.

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 → made their first commit to this issue’s fork.

Branch 5.x is Commerce 3 + D11 compatible.

alorenc → changed the visibility of the branch project-update-bot-only to hidden.

First, we need to commit #3396336 as it fixes pipeline issues

The new version 1.1.12 has added support for Drupal 11.

stefanos.petrakis → made their first commit to this issue’s fork.

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

The easy way to use an issue fork is to use the chx/drupal-issue-fork composer plugin.

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

Hi all,
I’m gonna update it in few minutes.
New release for Drupal 11 coming soon.

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!

rajas samse → made their first commit to this issue’s fork.

vladimiraus → changed the visibility of the branch project-update-bot-only to hidden.

when will the module be ready for version 11?
thank you

No update here?
Thank you for this great module

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.

Closing this in favour of 📌 Automated Drupal 11 compatibility fixes for redirect_metrics Needs review
New release 2.0.3 should be available today.

New release 2.0.3 should be available today.

Closing this in favour of 📌 Automated Drupal 11 compatibility fixes for redirect_metrics Needs review

I did a quick test on local, looks good.
I've merged the PR and will cut the new release.

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 .

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

This patch works to allow for installation on D11.

Fix applied to 2.1.

Changes are correct, marking as RTBC.

Tests are passing for D10 and D11, ready for review.

vasyl.kletsko → closed merge request !3

Hi!

Can we merge the branch please?

Any updates on D11 compatibility?

alorenc → changed the visibility of the branch project-update-bot-only to hidden.

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.

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.

vinodhini.e → made their first commit to this issue’s fork.

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

Moved to “Needs Work” because the current state generates a fatal error.

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 200

In 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 D11

First, 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.

alorenc → changed the visibility of the branch 3433991-automated-drupal-11 to hidden.

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).

When can we expect this issue to be fixed into a proper release to support Drupal 11 compatibility?

When can we expect this issue to be fixed into a proper release to support Drupal 11 compatibility?

When can we expect this issue to be fixed into a proper release to support Drupal 11 compatibility?

When can we expect this issue to be fixed into a proper release?

Hi, @zhelmet , Could you please provide it as a merge request?

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.