Skip to content
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

Plugin Mutations (activate/de-activate) #180

Open
jasonbahl opened this issue Jul 26, 2017 · 2 comments

Comments

Projects
3 participants
@jasonbahl
Copy link
Collaborator

commented Jul 26, 2017

Properly authenticated users should be able to activate/de-activate plugins via mutation.

@jasonbahl jasonbahl added this to the 1.0 release milestone Jul 26, 2017

@jasonbahl jasonbahl modified the milestones: 1.0 release, 1.1 Release Sep 12, 2017

@jasonbahl jasonbahl added this to To do in Roadmap Mar 20, 2018

@kidunot89

This comment has been minimized.

Copy link
Member

commented Jul 12, 2018

I'm working on the mutations as well as the install/uninstall mutations.

@CodeProKid

This comment has been minimized.

Copy link
Member

commented Jul 12, 2019

Note that these mutations should only happen on regular plugins, and not drop-ins or mu-plugins. If a client attempts this mutation on one of those kinds of plugins, we should return a helpful error message like: Sorry could not perform {$action} on {$plugin_name} because it's a {$plugin_kind}, which does not accept mutations this may require an extra query to grab mu-plugins / drop-ins if the plugin isn't found, but I think it's worth it for more verbose / helpful error messaging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.