Feature: allow defining of settings capability for more granular access control #1599
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduces const WP_STREAM_SETTINGS_CAPABILITY to allow site owners to set more granular control on who can manage Stream's settings.
|
@spenserhale thank you for contributing. Here's a link to the related enhancement proposed https://github.com/hokoo by #1553 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Introduces optional constant WP_STREAM_SETTINGS_CAPABILITY to allow site owners to set more granular control over who can manage Stream's settings. It defaults to the existing
manage_optionsfor backward compatibility.Why
We run a large multisite and request the ability to have a custom capability name so we can filter access to Stream settings for our network and site admins based on user settings.
Checklist
contributing.md).