- Issue created by @project update bot
This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module β these changes make this module compatible with Drupal 11! π
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot β to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
This module is D11 ready now on
3.0.x
.I'll make a release as soon as possible when core is released.
Merci Mr. Robot !
- Status changed to Active
9 months ago 9:00pm 31 March 2024 - πΈπ°Slovakia poker10
@matthieuscarset It would be great if you can create the release you mentioned in #4. Thanks!
@poker10 thank you for the reminder.
I actually double check this module again core 11.x and it became useless so I removed the compatibility with Drupal 11.
There are no reasons to maintain this module for newest Drupal versions since this change : https://www.drupal.org/node/3381495 β
Closing this ticket.
Updating the module description to let people know about this change.
- πΈπ°Slovakia poker10
@matthieuscarset Thanks for the answer. The mentioned change record is a draft and the issue it is referencing is still not committed - π Untranslated menu items are displayed in menus Needs work . Until then, the module is still very usable to hide menu links which are not supposed to be displayed in a specific language. Thanks!
- πͺπΈSpain rodrigoaguilera Barcelona
Please re-add the D11-compatibility as this module is still useful in Drupal 11
I thought the patches provided in the original issue were enough to replace menu_manipulator.
I see there is recent activities and uncertainties so I understand why we want a D11 release.
I'll make one asap
- πͺπΈSpain rodrigoaguilera Barcelona
Thanks but I'm wondering if there is any reason in particular to drop D10 compatibility on this commit
https://git.drupalcode.org/project/menu_manipulator/-/commit/b8d5335e384...A Drupal 11 from Drupal 10 upgrade is much easier when you get all modules to be compatible with both versions and then just upgrade the core. Can you at least declare compatibility for Drupal ^10.3 ?
Additionally it is a bit confusing to have 3.1.x release on the 3.0.x branch. Maybe is time for a new branch.
If you don't want to be bothered it also fine I just want to note how other module maintainers manage their branches and releases.
Totally right, thank you for your reply.
It is better to have a D10+11 version for easy upgrade.
I am happy to make it in a new version 4.x
Release here: https://www.drupal.org/project/menu_manipulator/releases/4.0.0 β