Allow accessing the "Custom block library" page without "Administer blocks" permission

Created on 3 November 2017, about 7 years ago
Updated 18 April 2024, 7 months ago

Hi,

Following this issue #2890753: Access checks shouldn't require administer permission β†’ , it seems there is a need to access the "Blocks" on the "Custom block library" page without the required "Administer blocks" permission.
/admin/structure/block/block-content

I suggest this improvement goes into this issue for better tracking.

✨ Feature request
Status

RTBC

Version

1.0

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium ludo.r Brussels

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¨πŸ‡¦Canada joseph.olstad

    Just so our patches do not get forgotten:
    The WxT distribution is still using this, between 200 and 300 installs, multiple public sector organizations, multiple installs in each organization.

  • πŸ‡ΊπŸ‡ΈUnited States joshua.roberson

    This module's features are now in core as of 10.1.x-dev and the project page updated to "no longer needed" and a section added for "How to migrate to core permissions". As I recall, "View restricted block content" is the only extra permission. Core moved the "Custom blocks" page from under "Structure" to "Content", removing the need for the "Administer blocks" permission.

    I'm just wondering, is the core version not usable in this instance or is there something extra this module offers that is needed? As of WxT v5.2.0, it has a note that it's equivalent to v5.1.1 but against Drupal Core 10.2.x, so I would assume the same core feature is available.

  • πŸ‡ΊπŸ‡ΈUnited States erier

    I want to re-iterate patch #59 works well. I've seen others say #55 is good. Worth trying both.

  • πŸ‡ΊπŸ‡ΈUnited States firewaller

    Patch #59 works for us

Production build 0.71.5 2024