-
Notifications
You must be signed in to change notification settings - Fork 882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce user_has_cap
filter
#8055
Labels
Comments
Consider using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we use the
user_has_cap
filter to add the "sub" level capabilities (anything other thanwpseo_manage_options
) when the user has thewpseo_manage_options
capability, we can throw away theWPSEO_Capability_Utils
and just use thecurrent_user_can
function to handle all capabilities.When removing the
WPSEO_Capability_Utils
from the code, also make sure these are removed in Premium.Example code for
wpseo_manage_redirects
can be found in the following commit:https://github.com/Yoast/wordpress-seo-premium/pull/1386/commits/d6f509f50c692ac2320666d7eab17ece4f0bf77f
The text was updated successfully, but these errors were encountered: