WebDevStudios / WebDevStudios/custom-post-type-ui

Backup/Undo/Recovery options.

Open
#540 2 comments 0 reactions 1 assignee View on GitHub

@tw2113 is already working on this.

Since Aug 21, 2016.

enhancement second opinion
Dominant language
PHP
Stars
641
Forks
139
PR merge metrics
No merged PRs in 30d

Description

Combining many thoughts into one ticket that we can flesh out into individual tickets later if needed.

Eliminates #425, #508, #506.

"Backup/Recovery" tab in Tools section.

In this tab, we will present all the relevant settings, outlined below.

  • Checkbox whether to backup at all. (Need to decide on default).
  • Type of backup:
    • Database
    • File
  • Location for file backup. (Default wp-content/uploads).
  • Delete db options/backups on uninstall (Default unchecked).

Indicate backups would be "run" on every save.

File backup.

Utilize idea located at http://docs.pluginize.com/article/84-save-cptui-settings-data-to-file

If backups enabled, run fetch/file_put on both before and after hooks. This provides a before save version, and after save version. Saves in saved location.

Provide indication of "before" or "after" in file name used.

Separate out between post types and taxonomies

Database backup.

Utilize idea located at http://docs.pluginize.com/article/84-save-cptui-settings-data-to-file except save to new options.

If backups enabled, save to new options on both before/after hooks. This provides a before save version and after save version. Name option key appropriately based on "before" or "after".

Separate out between post types and taxonomies

Undo functionality.

If backups enabled, offer "restore previous settings" option on associated Import/Export pages. Indicate that it'd restore version of all post type/taxonomy options from before last save.

Popup confirmation

Once confirmed, fetch from "before" version of saved location(db or file), import as appropriate.

Delete upon uninstall

Add to uinstall process from WP core. Check for our confirmation to delete. If yes, delete ALL related OPTIONS. Still leave content.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.