Restore from Backup

Restore WordPress and/or WooCommerce content from a previously created backup with preview and confirmation.

Steps

1. List available backups

   • Show message: "Fetching available backups..."
   • Call backup_list MCP tool
   • If no backups found:
     • Inform user: "No backups found in [backup-path]/"
     • Suggest creating a backup first with /wc-wp:backup
     • Exit

2. Display backups to user

   • Present backups in a clear, organized format:

     Available Backups:
     
     1. Full Site Backup - 2025-12-25 10:30:45
        File: full_2025-12-25T10-30-45.json (2.4 MB)
        Created: 2 hours ago
     
     2. Products Backup - 2025-12-25 08:15:20
        File: products_2025-12-25T08-15-20.json (856 KB)
        Created: 4 hours ago
     
     3. Posts Backup - 2025-12-24 16:45:10
        File: posts_2025-12-24T16-45-10.json (1.2 MB)
        Created: 1 day ago
     
     4. Product #123 Backup - 2025-12-24 14:20:00
        File: product-123_2025-12-24T14-20-00.json (12 KB)
        Created: 1 day ago
     

   • Sort by creation date (newest first)
   • Show relative time ("2 hours ago", "1 day ago")
   • Include file size for context

3. Get user selection

   • If --backup argument provided, use that filename
   • Otherwise, ask user to select from the list or provide filename
   • Validate selection exists

4. Read and preview backup contents

   • Read the selected backup file to understand what it contains
   • Show a preview/summary to user:

     Backup Preview: full_2025-12-25T10-30-45.json
     
     This backup contains:
     - 45 posts
     - 12 pages
     - 38 products
     - 32 orders
     - 15 categories
     - 28 tags
     - 234 media items metadata
     
     Created: 2025-12-25 10:30:45
     From site: https://turri.cr
     

5. Explain restoration process and risks

   • CRITICAL: Clearly warn user about restoration:

     ⚠️  IMPORTANT: Restoration Details
     
     Restoring this backup will:
     - [Explain what will happen based on backup type]
     - Existing content may be overwritten or updated
     - This operation cannot be easily undone
     
     Best Practice:
     Before proceeding, I recommend creating a fresh backup of current content.
     

   • Ask if user wants to create a current backup first (highly recommended)
   • If yes, create backup using backup_create before proceeding

6. Confirm restoration

   • Ask explicit confirmation:

     Ready to restore from: [backup-name]
     
     This will restore [X items] from the backup.
     
     Are you sure you want to proceed? (yes/no)
     

   • Require explicit "yes" to proceed
   • If "no", ask if they want to select a different backup or cancel

7. Perform restoration

   • Show message: "Restoring from backup..."
   • Call backup_restore MCP tool with filename
   • Display progress if possible
   • Handle errors gracefully

8. Report results

   • Show detailed restoration results:

     ✓ Restoration completed!
     
     Results:
     - 127 items restored successfully
     - 0 items skipped
     - 0 errors
     
     Restored content:
     - Posts: 45
     - Pages: 12
     - Products: 38
     - Orders: 32
     
     The site has been restored to state from: 2025-12-25 10:30:45
     

   • If any errors occurred, list them clearly
   • If items were skipped, explain why

9. Post-restoration verification

   • Suggest user verify restored content:
     • "Check a few posts/products to confirm they look correct"
     • "Verify no unintended changes occurred"
   • Remind user they can restore from a different backup if needed
   • If they created a pre-restoration backup, remind them where it is

Example Usage

# Interactive mode - select from list
/wc-wp:restore

# Restore specific backup
/wc-wp:restore --backup full_2025-12-25T10-30-45.json

Important Notes

• Safety first: Always recommend creating a current backup before restoring
• Be extremely clear about what will happen during restoration
• Require explicit confirmation - never restore without asking
• Show comprehensive previews before restoring
• Handle errors gracefully and provide clear error messages
• Verbose output showing exactly what was restored
• Suggest verification steps after restoration
• Remind user that restoration is a significant operation

Error Handling

• Backup file not found: Show clear error, list available backups
• Corrupted backup: Explain issue, suggest trying different backup
• API errors during restoration: Show error, explain state may be partial
• Permission errors: Check API credentials, suggest re-running /wc-wp:init