#ProjectUpdateBotD11

s.ghannouch → closed merge request !1

Support for Drupal 8, 9 will be dropped and compatibility with Drupal 11 will be added in the 1.2.x branch, the old 1.1.x branch will stay as is.

@penyaskito: Sorry if I went to far out-of-scope by adding the gitlab-ci and tugboat files. I think once the MR is merged the open issue for adding a gitlab-ci file 📌 Configure gitlab CI Active can be closed.

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

Merged to branch 1.1.x.

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

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

This change is in MR https://git.drupalcode.org/project/elasticsearch_connector/-/merge_reque... . Should then this be merged and also Drupal 11 compatible version released? As the module fixes are already there, only tests are still pending

I've merged the changes to a new 3.0.x branch which dropped drupal 9 support. A new 3.0.0 release is available now.

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

@murilohp : i have created patch for the same , please look into it , if it is fine , please let me know.

@murilohp : still ihave got an errro when i am using dev branch , could you please check it , please help me to resolve this issue .

eli-t → closed merge request !1

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

2.0.x branch is already D11 compatible.

Whilst there is an MR, all it does is makes a return type explicit, which is not required for Drupal 11.

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

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

As of July 2025 this module is not yet available for Drupal 11.

FYI, if you need it now, I was able to use the module entity_body_class to do similar and it does support Drupal 11:
https://www.drupal.org/project/entity_body_class →

As of July 2025 this module is not yet available for Drupal 11.

FYI, if you need it now, I was able to use the module entity_body_class to do similar and it does support Drupal 11:
https://www.drupal.org/project/entity_body_class →

I have resolved the warnings generated by the Gitlab tests in “Fixing only issues of phpstan II (#537580)” with commit 2123196f. I tested it on my D11 site and it worked perfectly.

These warnings were:
- cspell
- eslint
- phpcs
- phpstan
- stylelint

Well done everyone! We got there in the end.

New release 3.0.0 coming imminently.

Adding credits

This issue is due to flysystem_s3 swapping out the deprecated \Drupal\flysystem\Plugin\ImageStyleGenerationTrait::generateImageStyle() for its nominated replacement generateImageUrl().

generateImageUrl() relies on the presence of the flysystem.image_style_redirect.serve route, which doesn't appear to always be dynamically generated:

return \Drupal::urlGenerator()->generate('flysystem.image_style_redirect.serve', $args, UrlGeneratorInterface::ABSOLUTE_URL);

flysystem_s3 will have to revert to the old function, and inform phpstan to ignore this deprecation.

This will stop flysystem_s3 from being compatible with flysystem 3.0.x until it is resolved.

issue fixed

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

gábor hojtsy → made their first commit to this issue’s fork.

Setting up with Drupal 10, flysystem 2.2.0-beta2 and flysystem_s3 2.1.3 and exactly the same settings.php configuration for flysystem works without the issue in #3430648-31: Automated Drupal 11 compatibility fixes for flysystem_s3 → so this doesn't look like config, and either an outstanding D11 issue in flysystem or flysystem_s3.

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

Due to 2.0.x not getting synced in a long time - will close.

marcus_johansson → closed merge request !643

Hi...

I'd very much like to use this module with Drupal 11; any plan to make this compatible with Drupal 11 in the near future?

Thanks in advance.
Kazuyoshi

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

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

Getting the following error on D11 when attempting to access the SendGrid settings page:

php.ERROR: ArgumentCountError: 
Too few arguments to function Drupal\Core\Form\ConfigFormBase::__construct(), 1 passed in
/var/www/html/web/modules/contrib/sendgrid/src/Form/SettingsForm.php on line 49 and exactly
2 expected in Drupal\Core\Form\ConfigFormBase->__construct() (line 44 of /var/www/html/web/core/lib/Drupal/Core/Form/ConfigFormBase.php).

Testing with flysystem 2.3.x and this MR, I can successfully upload image field images to S3.

However when trying to view such images I get error below.

Not sure if this is just a config issue on my test setup or a genuine D11 issue.

The website encountered an unexpected error. Try again later.

Symfony\Component\Routing\Exception\RouteNotFoundException: Route "flysystem.image_style_redirect.serve" does not exist. in Drupal\Core\Routing\RouteProvider->getRouteByName() (line 208 of core/lib/Drupal/Core/Routing/RouteProvider.php).
Drupal\Core\Routing\UrlGenerator->getRoute() (Line: 269)
Drupal\Core\Routing\UrlGenerator->generateFromRoute() (Line: 105)
Drupal\Core\Render\MetadataBubblingUrlGenerator->generateFromRoute() (Line: 96)
Drupal\Core\Render\MetadataBubblingUrlGenerator->generate() (Line: 94)
Drupal\flysystem_s3\Flysystem\S3->generateImageUrl() (Line: 227)
Drupal\flysystem_s3\Flysystem\S3->getExternalUrl() (Line: 75)
Drupal\flysystem\FlysystemBridge->getExternalUrl() (Line: 103)
Drupal\Core\File\FileUrlGenerator->doGenerateString() (Line: 66)
Drupal\Core\File\FileUrlGenerator->generateAbsoluteString() (Line: 255)
Drupal\image\Entity\ImageStyle->buildUrl() (Line: 302)
.
.
.

Merging.

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

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

Hi,

Is this module now Drupal 11 compatible? As that is true, please also change it on the project page. Thanks!
greetings,

Looks like the deprecations about which phpunit was complaining were in the custom phpunit.xml.dist file supplied with this project.

The merge pipeline now passes with that file removed.

PHPunit says we have 10 tests and 26 assertions all passing with this removed.
These are the same totals as before the phpunit.xml.dist was removed, so it looks like this file was unnecessary.

I am not aware of any more issues with this merge request.

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

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

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

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

ça n'a pas marché pour moi

smustgrave → closed merge request !5

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

Hi, could you please apply this fix and release the stable version? Thanks!

We are doing some issue management housekeeping and adding/removing components.

We are removing the "Code" component and want people to categorize issues with the best module/submodule component.

Moving this issue to "AI Core module".

See 📌 Update AI module project components Active for more details.

Rerolled against 3.3.x

We are doing some issue management housekeeping and adding/removing components.

We are removing the "Code" component and want people to categorize issues with the best module/submodule component.

Moving this issue to "AI Core module".

See 📌 Update AI module project components Active for more details.

We are doing some issue management housekeeping and adding/removing components.

We are removing the "Code" component and want people to categorize issues with the best module/submodule component.

Moving this issue to "AI Core module" as I'm not sure where the best place is.

If we have a new project to move this to, we can optionally do that as a secondary step.

See 📌 Update AI module project components Active for more details.

If you come across this, simply upgrade to toc_api ^2.0 which is supporting current Drupals

https://www.drupal.org/project/toc_api/releases/2.0.0 →

Done in 2.x branch.

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

Created the following patch with the changes on branch 3435719-d11-compatibility

Added compatibility with drupal 11.

• Modified the javscript to be cokmpatible with the eleven library.
• Modified the .info file
• Modified FileSystemInterface::EXISTSERROR constant.

You're right Murilo.
Thanks for the update.

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

@igorgoncalves the issue with using a direct link to the merge request (MR) is that I can't lock it to a specific version. If someone updates the MR, I'll always receive the latest version. This means if someone commits something incorrect, I'll end up with that version.

@brahmjeet789, the patch is basically the content of the merge request, since the MR is pointing to the dev branch, you'll have to use it, here I'm applying it to the dev-1.0.x#62e8dd618, my composer has the following requirement

"drupal/quickedit": "dev-1.0.x#62e8dd618516b8f177615cac26d6ccefe21e067a",

I hope this helps you. And moving this back to RTBC

Hi @brahmjeet789, Murilo just tried to give us another way to fix with the MR we currently have.

did you tried to check the proposal MR with the steps at #27?

@mutilohp: i am not able to apply patch , please check my screenshot for the same , please let me know if am doing anything worng in the project.

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

Looks good, works fine. Pumping the priority so this module can be installed via composer on D11 sites.