- 🇺🇸United States scott_earnest
thank you @themusician for pointing that out
you should now see the following in the patch:ableplayer V4.5.1 with DOMPurify included
Also, I decided to re-do the patch off of their main branch. When submitting an MR for Ableplayer they ask you branch of off develop, but for the purposes of the Drupal module I felt it was best to branch from the stable release. Please let me know your thoughts on that.
Thank you! new patch attached.
- 🇺🇸United States laura.gates
Neither #5 or the MR9 (project-update-bot-only) Diff apply as patches with Drupal 10.4.6
-
apotek →
committed 262e8e2b on 2.x authored by
project update bot →
Issue #3434172 by project update bot, apotek: Automated Drupal 11...
-
apotek →
committed 262e8e2b on 2.x authored by
project update bot →
- 🇲🇽Mexico gnuget Puebla
It seems that the only change needed was in the `info.yml` file, so I think this is ready for a small release.
I'm going to create it soon.
-
berdir →
committed 8dcd621c on 8.x-1.x authored by
project update bot →
Issue #3435480: Automated Drupal 11 compatibility fixes for...
-
berdir →
committed 8dcd621c on 8.x-1.x authored by
project update bot →
- First commit to issue fork.
- First commit to issue fork.
- @mstenta opened merge request.
-
aaronchristian →
committed 2a3d4580 on 1.x
Issue #3428290: Automated Drupal 11 compatibility fixes for...
-
aaronchristian →
committed 2a3d4580 on 1.x
- 🇺🇸United States DamienMcKenna NH, USA
This change is already present in the latest release, 8.x-1.8.
- 🇺🇸United States m.stenta
@dmitry.korhov It isn't the
getSupportedTypes()
method that's at issue, it is thenormalize()
method.See this commit in the MR: https://git.drupalcode.org/issue/jsonapi_schema-3431487/-/commit/7f424f1...
(Originally cherry-picked from 🐛 PHP8.3 compatibility issues Active )
This is the fatal error that it fixes:
Fatal error: Declaration of Drupal\jsonapi_schema\Normalizer\DataDefinitionNormalizer::normalize($entity, $format = null, array $context = []) must be compatible with Symfony\Component\Serializer\Normalizer\NormalizerInterface::normalize(mixed $data, ?string $format = null, array $context = [])
Is there a way to support that in Drupal 10 and 11? I would be happy to adjust the MR if there is, but if not then I think this is the best we can do.
- 🇵🇱Poland dmitry.korhov Poland, Warsaw
@m.stenta
Other modules with the same issue addressed are compatible for both 10.3 and 11 versions of Drupal.
So I see no reasons of dropping support of 10.3 for this module as well. See https://git.drupalcode.org/project/rest_views/-/merge_requests/19/diffs#... ( https://www.drupal.org/project/rest_views/issues/3451283 📌 Automated Drupal 11 compatibility fixes for rest_views Active ) - 🇺🇸United States dave reid Nebraska USA
Merged the changes and will tag a new release shortly here.
-
dave reid →
committed fdd82eae on 2.x authored by
project update bot →
Issue #3434865: Automated Drupal 11 compatibility fixes for...
-
dave reid →
committed fdd82eae on 2.x authored by
project update bot →
- First commit to issue fork.
- 🇺🇸United States dave reid Nebraska USA
dave reid → made their first commit to this issue’s fork.
- 🇺🇸United States kerrymick Chicago
I can confirm that this patch works well on D11 sites. Tested on 2 sites.
- @dimas11 opened merge request.
- First commit to issue fork.
- leymannx Berlin
Provided new MR with info.yml changes done as well. Also removed composer.json which had differing version constraints. composer.json file will get created automatically from drupal.org infra pipelines. You only need to have it, if you have additional PHP dependencies.
Let's get this merged and released. 🙏🏻
- @normanlol opened merge request.
- leymannx Berlin
norman.lol → made their first commit to this issue’s fork.
Automatically closed - issue fixed for 2 weeks with no activity.
Tested. The error message that appears as a result of the test is as follows.
Fatal error: Declaration of Drupal\link_allowed_hosts\Plugin\Validation\Constraint\LinkAllowedHostConstraint::getDefaultOption() must be compatible with Symfony\Component\Validator\Constraint::getDefaultOption(): ?string in /var/www/html/d11site/web/modules/contrib/link_allowed_hosts/src/Plugin/Validation/Constraint/LinkAllowedHostConstraint.php on line 41
- 🇨🇦Canada phjou Vancouver 🇨🇦 🇪🇺
Added drupal 11 compatibility - drupal 8 and 9 dropped since they are deprecated
- First commit to issue fork.
- 🇺🇸United States redeight
There is a new version of Block Class. We should depend on that one, 4, not 2 which is no longer marked as supported and is recommended to upgrade directly to 4.
- 🇬🇧United Kingdom JamesOakley Kent, UK
So basically, it's ready to roll, it just needs the info file updating to say as much.
Hello @maintainer,
Can we have a official drupal 11 release of this module?- 🇬🇧United Kingdom somersoft
I have run the upgrade_status → on D11.1.6 for this packge and the report is
CONTRIBUTED PROJECTS
--------------------------------------------------------------------------------
Menu Export project-update-bot-only-dev
Scanned on Mon, 28/04/2025 - 12:47.1 warning found.
web/modules/contrib/menu_export/menu_export.info.yml:
+----------------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+
| status | line | message |
+----------------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Check manually | 5 | Value of core_version_requirement: ^8 | ^9 | ^10 | ^11 is not compatible with the next major version of Drupal core. See https://drupal.org/node/3070687. |
+----------------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+which indicates that currently it is also will run on D12 as well. This report does not report on changing underlying functionality.
Report from running the tests for the package.
docker@cli:/var/www$ phpunit web/modules/contrib/menu_export/
PHPUnit 10.5.45 by Sebastian Bergmann and contributors.Runtime: PHP 8.3.20
Configuration: /var/www/phpunit.xml.dist. 1 / 1 (100%)
Time: 00:08.321, Memory: 12.00 MB
OK, but there were issues!
Tests: 1, Assertions: 15, PHPUnit Deprecations: 1. - 🇳🇿New Zealand davidwhthomas
Tested and working with Drupal 11!
With thanks for the useful (essential) module.
- 🇬🇧United Kingdom somersoft
@jamesoakley from the rector patch → and merge request, the menu_export.info.yml file needs to report that it is compatible with D11 and remove the core information.
diff --git a/menu_export.info.yml b/menu_export.info.yml index 9a41318..729c819 100644 --- a/menu_export.info.yml +++ b/menu_export.info.yml @@ -2,6 +2,5 @@ name: Menu Export type: module description: 'This module exports and imports menus and menu links.' package: Development -core: 8.x -core_version_requirement: ^8 || ^9 || ^10 +core_version_requirement: ^8 || ^9 || ^10 || ^11 #configure: maintenance_notifications.form
Once that change is made to or merged into 8.x-1.x branch and tagged(?) then magic can happen and the package indicates that compatible with the list of Drupal version on the package page. Drupal's composer end-point will also report that it requires core one of those core version too.
- 🇬🇪Georgia glontianano
We use the patch successfully on Drupal 11 project and can confirm that it solves the compatibility issue.
- 🇬🇧United Kingdom JamesOakley Kent, UK
Can someone please clarify exactly what still needs to be done to make the module D11 compatible?
- 🇬🇧United Kingdom somersoft
@smustgrave At this moment composer.json is needed as the repository is a part of a web site project's composer.json's respositories section and to get a set of packages that composer is happy with.
"repositories": [ { "type": "vcs", "url": "https://git.drupalcode.org/issue/menu_export-3431947.git" } ], require: { "drupal/menu_export": "dev-project-update-bot-only" }
Once it has been merged in then Drupal end-point service for 8+ will indicate that it compatable with core ^11 because of the update to menu_export.info.yml. At that point, as there are no dependencies, it can be removed.
- 🇺🇸United States apotek
This set of changes has been tested and the module works under Drupal 11.
Interesting, I came to this module following a request to have something like it in core: https://www.drupal.org/project/drupal/issues/2874548 ✨ Add a choice to use UUID in entity reference values instead of the entity's ID Needs work
A non profit wanted to use views data export to CSV with UUID then import thousands of nodes into Drupal 11 and reference them with UUID instead of entity Id for other content types... Hoping you can get this to D11 officially.
-
vivianspencer →
committed 43312d9c on 2.0.x
Issue #3435368: Automated Project Update Bot fixes from run 11-127659.
-
vivianspencer →
committed 43312d9c on 2.0.x
- @vivianspencer opened merge request.
- 🇺🇸United States dcam
That didn't work either.
Fine. We'll do this the old-fashioned way.
Thank you to everyone who worked on this issue!
- 🇺🇸United States dcam
Something is wrong with MR 15. I've tried several times to use the merge tool, but it keeps failing. It's possible that all the mangling of that branch is causing an issue. So I opened a new MR 24.
- @dcam opened merge request.
- 🇺🇸United States dcam
I've been allowed to maintain the module. FYI, I'm removing the composer.json file, but I'll add it in a separate issue. I'd rather maintain separation of concerns so that changes are easier to revert with Git.
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇺🇸United States BenStallings
The submodules also need their core_version_requirement updated.
- 🇺🇸United States BenStallings
I'm now seeing,
Call to deprecated method generateImageStyle() of class Drupal\flysystem_s3\Flysystem\S3. Deprecated in flysystem:2.2.0 and is removed from flysystem:3.0.0. Adapters should use generateImageUrl() to enable non-blocking image uploads.
on line 227 of S3.php. I'll see if I can fix it.
-
b_sharpe →
committed 4605b59a on 2.0.x
Issue #3431829 by dieuwe, darvanen: Automated Drupal 11 compatibility...
-
b_sharpe →
committed 4605b59a on 2.0.x
- @rickydev90 opened merge request.
- 🇬🇧United Kingdom ricky@rbwebdesigns.co.uk
rickydev90 → made their first commit to this issue’s fork.
- 🇩🇪Germany kmetz
Two automated D11 compatibility issues were created for some reason – I'm closing this one as a duplicate of https://www.drupal.org/project/betterlogin/issues/3428257 📌 Automated Drupal 11 compatibility fixes for betterlogin Active (which has more details).
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.
Automatically closed - issue fixed for 2 weeks with no activity.
- 1812ece4 committed on 8.x-1.x
Issue: #3434075, Security: #178773, Security: #178774
- 1812ece4 committed on 8.x-1.x
- First commit to issue fork.
- @setheshaw opened merge request.
- 🇺🇸United States seth.e.shaw
seth.e.shaw → made their first commit to this issue’s fork.
- @chris-dart opened merge request.
- First commit to issue fork.
- 🇺🇸United States Chris Dart
chris dart → made their first commit to this issue’s fork.
- 🇨🇦Canada joseph.olstad
For comment #45
🐛 Fatal error after updating to toc_api:^2 Active
and
🐛 Layout builder fatal error Active Automatically closed - issue fixed for 2 weeks with no activity.
- @manueladan opened merge request.
- 🇪🇸Spain manuel.adan 🌌
manuel.adan → changed the visibility of the branch 3433995-automated-drupal-11 to active.
- 🇪🇸Spain manuel.adan 🌌
manuel.adan → changed the visibility of the branch 3433995-automated-drupal-11 to hidden.
- 🇪🇸Spain manuel.adan 🌌
manuel.adan → made their first commit to this issue’s fork.
- First commit to issue fork.
- 🇪🇸Spain omarlopesino
I added a composer.json file to be able to require the module through composer
- First commit to issue fork.
-
geoanders →
committed 3e7fa544 on 8.x-2.x
Issue #3429839: Automated Drupal 11 compatibility fixes for dev_mode.
-
geoanders →
committed 3e7fa544 on 8.x-2.x
- 🇭🇰Hong Kong hswong3i
Sorry @dcam, i give a re-rollback with composer.json so it could be install normally with (also giving it a
git rebase -i origin/2.x
into single GIT commit):{ "repositories": { "https://drupal.org/node/3434813": { "canonical": false, "type": "vcs", "url": "https://git.drupalcode.org/issue/styleguide-3434813.git" }, }, "require": { "drupal/styleguide": "dev-project-update-bot-only", }, }
- 🇨🇦Canada geoanders Nova Scotia 🍁
Will review tomorrow and get merged in. Thanks!
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇺🇸United States uptil4music
@rodrigoaguilera Any chance you could create a new release, please?
- 🇺🇸United States m.stenta
@dmitry.korhov See my comment #10 above.
Drupal 11 upgrades Symfony from version 7, which changes the method signatures in Symfony's
NormalizerInterface
. I think this means we need to drop support for Drupal 10.