- π¬π§United Kingdom SirClickALot Somerset
I'm just nudging about a Drupal 10 version because what I find is that when you have a lot of modules and permission in play, this really is the only module that makes the Permission page usable.
Neither Permissions Filter β nor Fast Permissions Administration β do the job as far s I can see because both of them require the whole 'array' of permissions to loaded up front and therein lies the real memory/speed problem.
To my mind this is an essential going for ward to D9 and AND D10+
- πΊπΈUnited States justcaldwell Austin, Texas
Hi @SirClickALot, if you're able, please review π Automated Drupal 10 compatibility fixes Fixed and mark RTBC if appropriate. That might help push along a D10 release. Thanks!
- π¬π§United Kingdom SirClickALot Somerset
Hi @Michael β
Still cannot install even the DEV version on my local Drupal 10.0.3...
composer require 'drupal/filter_perms:1.x-dev@dev'
Results in...
Problem 1 - drupal/filter_perms dev-1.x requires drupal/core ^8 || ^9 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev] but the package is fixed to 10.0.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command. - drupal/filter_perms 1.x-dev is an alias of drupal/filter_perms dev-1.x and thus requires it to be installed too. - Root composer.json requires drupal/filter_perms 1.x-dev@dev -> satisfiable by drupal/filter_perms[1.x-dev (alias of dev-1.x)].
- πΊπΈUnited States justcaldwell Austin, Texas
Hi Nick,
Yeah, the DEV branch still has the ^8 || ^9 constraint. You need the code in the issue fork associated with π Automated Drupal 10 compatibility fixes Fixed . A few options, in order of complexity:- Use git to clone the issue fork repo into your project (be sure to check out the
3297235-automated-drupal-10
branch). This skips Composer, but is good for a quick test. - Install the DEV branch with Composer using composer-drupal-lenient plugin, then apply the MR3 patch from the issue branch to get the D10 updates.
- Modify your composer.json β to get Composer to install the issue fork code.
- Use git to clone the issue fork repo into your project (be sure to check out the
- π¬π§United Kingdom SirClickALot Somerset
Hi Michael,
I have now grabbed the code from the
filter_perms-3297235
branch and installed manually in a local dev site but I still cannot get it installed even in a clean D10 because the .info.yml only includes...core_version_requirement: ^8 || ^9
Adjusting to...
core_version_requirement: ^8 || ^9 || ^10
...of course sorts that but it's a botch ;-(
Maybe it's just me but I as far as I can see the core
/admin/people/permissions
form is just unusable in D10 if you have anything like a real life number of roles and modules in action. Is there any other way pre-filter the permissions page down or is Filter Permissions really the crucial module I think it is because none of the other Permission page enhancing modules that I have looked at do the same kind of pre-filtering?Thanks again
- πΊπΈUnited States justcaldwell Austin, Texas
Hi Nick,
It's not just you. We have a fairly large number of permissions and modules, and the permissions form is unusable without filter_perms. It's been a while since I tried some other permissions-related modules (e.g. Permissions Filter β or Fast Permissions Administration β ), but, if I remember correctly, neither of those pre-filter the form on load, so they didn't address our issue.Permissions filtered by modules β is a newer option that wasn't around when I was first searching for a solution. May be worth giving it a shot?
As for the issue branch code. I'm not sure why you're not getting the changes. It definitely has the updated core version requirement (here's the info.yml code). If you're cloning from git, maybe you just need to switch to the issue branch, since 8.x-1.x is the default? I tried to download the issue branch code directly, but got an error. So I guess it's not easy/possible to download the code in an issue branch.
If there's not movement in the near future, I may apply for maintainer just to get the Drupal 10 changes pushed out.
- Status changed to Fixed
almost 2 years ago 1:18pm 16 June 2023 - πΊπΈUnited States justcaldwell Austin, Texas
8.x-1.0-alpha2 β is Drupal 10 compatible. Thanks!
Automatically closed - issue fixed for 2 weeks with no activity.