-
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
Add deactivate-intent to plugin deactivation #9824
Comments
Watch for GDPR pitfalls. Sending this feedback anonymously still transmits a lot of information that might or might not be problematic:
|
Just going to pop in, I find these popups to be utterly annoying and frustrating when disabling plugins. |
More thoughts. I'm reasonably confident that few people understand that deactivating the plugin "un-SEO's" their site; we should throw some warnings/notifications to make this clear - perhaps with greater priority than seeking feedback. I'll aim to scope more specifically later this week. |
When disabling the plugin we want to provide the user with a modal in which the intent of the deactivation can be supplied.
The plugin Monster Insights is providing this functionality already and is the inspiration for this feature:
![disable-monster-insights](https://user-images.githubusercontent.com/2005352/40425420-998f849e-5e98-11e8-86c8-c680f6b056dd.jpg)
The options provided to the user should be checked with the Product-team before merging.
The code that is being used in the Monster Insights plugin should be taken as a base.
The information should be sent anonymously to Yoast.com to add it to our logging system.
The text was updated successfully, but these errors were encountered: