Add Capability-Based Block Display Options

[qarayahya]

What problem does this address?

Currently, Block Visibility allows displaying blocks based on various criteria, such as user roles, page types, etc. However, it lacks the ability to control block visibility based on user capabilities. This limitation can be problematic when you want to display certain blocks only to users with specific permissions, regardless of their role.

What is your proposed solution?

Introduce a new capability-based option for displaying blocks. This option would allow users to specify a capability (e.g., "read_premium_posts") and only display the block if the current user has that capability.

Example:

• Capability Field: Provide a field to input the desired capability slug (e.g., "read_premium_posts").

[ndiego]

This should be relatively easy to add, but there are a lot of user capabilities in WordPress. Do you imagine this being a dropdown containing all Core capabilities or a text field? A text field is not as user-friendly, but this would allow BV to support custom capabilities. 🤔

[qarayahya]

I’d go with a text field. It’s cleaner and supports custom capabilities. Maybe adding autocomplete for core capabilities could make it more user-friendly?

[elyran]

I vote for a text field. Simple and fast.

[MadtownLems]

I support a text field for this. Capabilities are natively confusing enough. This is an advanced feature, and it's totally fine to require someone to know the specific capability name. It might even help prevent people from choosing a capability from the dropdown that they're not entirely sure what it means!

I assume the idea here is only accepting a capability name, such as edit_published_pages. Note that complete capability checking sometimes involves arguments, such as determining if the current user can edit post with ID X.