-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Site settings: Allow site with premium theme to be deleted with proper warnings #17012
Labels
Comments
kriskarkoski
added
[Feature] Site Settings
All other general site settings.
[Type] Bug
labels
Aug 8, 2017
This was referenced Aug 8, 2017
apeatling
modified the milestones:
Product Quality,
Product Quality: Setting up My Site Flows
Jan 31, 2018
Another one on 2272156-hc |
Another report 1056399-zen |
This happened with another site: 1077287-zen |
Just noting this is now also causing issues with account closure, for example, https://en.forums.wordpress.com/topic/closing-account-58/ |
Thank you, @bluefuton! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In adding a warning when deleting a site with a Premium theme we have blocked sites with only a Premium theme from deleting their site. The message is generic for all upgrades and advises the user to cancel the upgrade before deleting their site. However, premium themes are a one-time purchase and we do not support deleting them.
#9639 was opened to allow premium themes to be canceled, but given the difficulty for staff to restore them in the case of accidental cancellation and potential loss of settings when this happens I think we should instead allow sites with only premium theme(s) to delete their site as they could previously, but with proper warning that the site has a premium theme and access to it will be lost.
Steps to reproduce
What I expected
To be able to delete a site with a premium theme with proper warnings that I would lose access
What happened instead
The user is shown a message to cancel the upgrades that cannot be done on their own and requires support intervention
The text was updated successfully, but these errors were encountered: