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

Inform Users of First Backup/First Restore Point for Paid Plans #12402

Open
drwpcom opened this issue May 17, 2019 · 0 comments
Open

Inform Users of First Backup/First Restore Point for Paid Plans #12402

drwpcom opened this issue May 17, 2019 · 0 comments
Labels
[Feature] Backup & Scan [Pri] Low [Status] Needs Design [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it

Comments

@drwpcom
Copy link

drwpcom commented May 17, 2019

Issue:

After a site goes AT or a user upgrades Jetpack to a paid plan, it is unclear to users at what point backups become available.

Possible solution:

Show a message to users informing them that the first backup is running and changes made before its completion cannot be undone. Possible to options to do this include:

  • a persistent message in WP Admin until the backup is done since it's likely that users will be making changes after installing their first plugin/custom theme.
  • a one-time message on the post plugin/theme install page in Calypso saying the backup takes some time to complete.

This issue is a result of a conversation between @kriskarkoski, @tmmbecker, @seear and me in 3814-gh-jpop-issues.

@tmmbecker tmmbecker added [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it [Feature] Backup & Scan [Status] Needs Design labels May 17, 2019
@joanrho joanrho assigned joanrho and unassigned joanrho May 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Backup & Scan [Pri] Low [Status] Needs Design [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it
Projects
None yet
Development

No branches or pull requests

4 participants