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

Add deactivate-intent to plugin deactivation #9824

Open
moorscode opened this issue May 23, 2018 · 3 comments
Open

Add deactivate-intent to plugin deactivation #9824

moorscode opened this issue May 23, 2018 · 3 comments

Comments

@moorscode
Copy link
Contributor

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

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.

@schlessera
Copy link
Contributor

schlessera commented May 23, 2018

Watch for GDPR pitfalls. Sending this feedback anonymously still transmits a lot of information that might or might not be problematic:

  • a given user with IP (A)
  • was using plugin (B)
  • while using the browser (C)
  • on the platform (D)
  • and stopped using the plugin because (E)

@Volnus
Copy link

Volnus commented May 28, 2018

Just going to pop in, I find these popups to be utterly annoying and frustrating when disabling plugins.

@jonoalderson
Copy link

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.

@Djennez Djennez removed the backlog label Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants