-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add Capabilities #99
Comments
The first question is what permission is analogous to what... going to map out in this issue |
Microsub defines the following scopes: read - this is the minimum scope clients should request. this allows clients to have read access to channels. follow - allows the client to manage the following list mute - allows the client to mute and unmute users block - allows the client to block and unblock users channels - allows the client to manage channels |
That would suggest capabilities of read_microsub_channels, manage_microsub_channels to start |
For follow, you have edit_microsub_channels, matching the WordPress naming conventions |
There is no real analogue for blocking and muting, so mute_microsub_channels and block_microsub_channels |
That means that all capabilities are working on the microsub_channels... which currently are a post type and can be mapped to post capabilities |
Since Microsub has no parallel inside the WordPress permission system, the plugin needs to add capabiltiies to the standard user roles that reflect the various functions and map them appropriately using map_meta_cap
The text was updated successfully, but these errors were encountered: