- Issue created by @project update bot
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass 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-120835This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - πΊπΈUnited States sarahwylie
I could not get this patch to work on my local. Will revisit possible alternative solutions when I'm able.
- πΊπΈUnited States joshua.roberson
Per the project page, this module's functionality is apart of Drupal 10.1.x-dev. This project is no longer needed for newer Drupal versions. Closed as "won't fix".
- πΊπΈUnited States judyakers
There are custom user roles that were created for my website that have values set in admin/people/permissions/module/block_content_permissions . When I uninstall and remove it, those permissions go away.
Is there a way to port those configuration values to block_contents for those custom users?
- πΊπΈUnited States joshua.roberson
Answered #6 at 3486240 π¬ Custom User roles permissions lost Active .
- Status changed to Closed: won't fix
2 months ago 10:18am 8 April 2025 - π«π·France Fabsgugu
The Issue is closed, changing its priority is unnecessary.
The feature is now part of the core, so migrating the module is not necessary. Simply remove the module and switch to the core feature.
- π―π΄Jordan Rajab Natshah Jordan
Noted;
Doing that for sure.
Exploring to find a smoother way to migrate.Maybe it needs a hook update, or a custom drush command to help migrating to Drupal Core.
Before disabling the module.Moving the conversation to π¬ Custom User roles permissions lost Active