Group list empty after 1.x→2.1 upgrade

Created on 16 August 2023, 11 months ago
Updated 17 August 2023, 11 months ago

Problem/Motivation

We recently upgraded a site from Group 8.x-1.x to 2.1.

After the migration the group list ("/admin/group") no longer displays our groups, but just shows an empty list.

Further, if I visit a known group entity page (e.g. "/group/131") I'm given an Access Denied, even as an administrator. (And the watchdog message wasn't helpful on where to look for clues.) I know the group still exists because I can load it ("\Drupal::entityTypeManager()->getStorage('group')->load(131)->label();" displays the group name).

All of the upgrade hooks worked as far as I can tell; but perhaps there was a silent failure somewhere?

Any ideas as to where to look to isolate this bug?

πŸ’¬ Support request
Status

Closed: works as designed

Version

2.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States seth.e.shaw

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @seth.e.shaw
  • πŸ‡ΊπŸ‡ΈUnited States seth.e.shaw

    Slowly tracking this down. I've determined that the CalculatedPermissionsItem is not setting isAdmin to TRUE in GroupPermissionChecker::hasPermissionInGroup() as I would expect.

    This appears to be because Group uses isAdmin in the Group context (https://git.drupalcode.org/project/group/-/blob/2.1.0/src/Access/Synchro...) rather than in the Site context.

    Is there any way for a site administrator to govern groups that may potentially no longer have active admins/owners? I figure a site admin should at least be able to see them.

  • I figure a site admin should at least be able to see them.

    that's one of the big changes between Group module versions.

    See here also: https://www.drupal.org/project/group/issues/3315050 πŸ’¬ Sitewide Administrator permissions not working Closed: works as designed

  • Status changed to Closed: works as designed 11 months ago
  • πŸ‡ΊπŸ‡ΈUnited States seth.e.shaw

    Ah, I see. I did read through the release notes but missed the implications of "Access bypass permission is gone" for us. Our use-case does require admins to access all groups, so I'll have to look at the linked documentation for bringing it back.

    That said, it would have been helpful of the release notes to link documentation on doing this rather than having to look through the issues to find it. I didn't find the issue you linked, because I was looking for a 2.x issue.

Production build 0.69.0 2024