{"id":11618,"date":"2026-07-12T04:06:03","date_gmt":"2026-07-11T20:06:03","guid":{"rendered":"https:\/\/aeosub.com\/splendorbackups-for-ai1wm\/"},"modified":"2026-07-12T04:06:03","modified_gmt":"2026-07-11T20:06:03","slug":"splendorbackups-for-ai1wm","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/splendorbackups-for-ai1wm\/","title":{"rendered":"SplendorBackups – Automatic Backups for All-in-One WP Migration and Backup"},"content":{"rendered":"
\"SplendorBackups<\/div>\n
\n
LethaldiranMX Insight<\/div>\n
\n
\n

SplendorBackups addresses a notable gap in the free tier of All-in-One WP Migration by introducing a robust, local scheduling engine directly tied to the core plugin’s export framework. By leveraging the existing, highly reliable export classes of All-in-One WP Migration, it provides administrators with automated, retention-controlled backups without the overhead of a completely separate backup engine. It serves as a practical operational utility for site owners who want to automate their migration-ready archives locally while maintaining strict data sovereignty and detailed audit logs of backup activities.<\/p>\n

Best Fit & Operational Role:<\/strong> This plugin is best suited for agency partners and solo administrators who already rely on All-in-One WP Migration for manual migrations but require automated, hands-off local recovery points. It fits seamlessly into a standard WordPress stack as an orchestration layer rather than a standalone backup solution, solving the operational challenge of manual export fatigue. It is ideal for environments where data sovereignty is paramount, as it keeps all archives on-premise within the default directory without external cloud dependencies.<\/p>\n

Potential Limitations & Pitfalls:<\/strong> Because this plugin relies entirely on the host server’s resources and WordPress Cron to trigger the export classes, resource-constrained hosting environments may experience timeouts or skipped runs during large site exports. Additionally, keeping backups strictly local means administrators must implement their own offsite synchronization strategy, as a complete server failure would compromise both the live site and the local backup directory.<\/p>\n<\/div>\n<\/div><\/div>\n

\n
\n \"SplendorBackups <\/p>\n
\n
Plugin Specification<\/div>\n

WordPress.org Official Data<\/small>\n <\/div>\n<\/p><\/div>\n\n\n\n\n\n\n\n
Developer<\/th>\nsplendorsoft<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv1.0.0<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n5.8 \/ 7.0.1<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-07-11 8:02pm GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details -><\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
Schedule automatic local backups for AI1WM \/ All-in-One WP Migration and Backup with retention, logs, and admin-only backup management.<\/div>\n

SplendorBackups for AI1WM \/ All-in-One WP Migration and Backup adds a focused scheduling layer for sites that already use All-in-One WP Migration and Backup.<\/p>\n

The plugin can queue recurring All-in-One WP Migration exports, keep a separate list of backups created by this plugin, apply a retention limit, and show admin activity logs for backup starts, completions, failures, skipped runs, downloads, deletions, and retention cleanup.<\/p>\n

It is built for site owners and administrators who want automatic backups for AI1WM \/ All-in-One WP Migration and Backup, scheduled backups for migration archives, and a simple way to track backup activity from the WordPress dashboard.<\/p>\n

Backup files are stored in the standard All-in-One WP Migration backup folder:<\/p>\n

wp-content\/ai1wm-backups\/\n<\/code><\/pre>\n
This plugin does not replace All-in-One WP Migration and Backup. It requires All-in-One WP Migration and Backup to be installed and active, and it uses that plugin’s export and backup-file handling.<\/p>\n
The plugin does not send backup files, settings, logs, or site data to Splendorsoft or any external service. All backup files remain on the WordPress server unless an administrator downloads or moves them.<\/p>\n
Features<\/h3>\n
    \n
  • Hourly, twice daily, daily, weekly, or monthly backup schedules.<\/li>\n
  • Manual “Run backup now” action for administrators.<\/li>\n
  • Retention limit for completed backups created by this plugin.<\/li>\n
  • Optional exclusion of spam comments and post revisions.<\/li>\n
  • Separate admin list for backups created by this plugin.<\/li>\n
  • Activity logs for backup starts, completions, failures, skipped runs, downloads, deletions, and retention cleanup.<\/li>\n
  • Compatibility status panel for required All-in-One WP Migration classes, constants, and helper functions.<\/li>\n
  • Admin-only download and delete actions protected by WordPress capabilities and nonces.<\/li>\n<\/ul>\n
    Support and Troubleshooting<\/h3>\n
    Before relying on scheduled backups, open the Compatibility status panel and run a manual backup on the target site. If a backup does not complete, check the activity logs, the All-in-One WP Migration Backups page, the wp-content\/ai1wm-backups\/<\/code> folder, WordPress cron, loopback requests, disk space, and host timeout\/resource limits.<\/p>\n
    Requirements<\/h3>\n
      \n
    • WordPress 5.8 or higher.<\/li>\n
    • PHP 7.4 or higher.<\/li>\n
    • All-in-One WP Migration and Backup installed and active.<\/li>\n
    • A writable wp-content\/ai1wm-backups\/<\/code> folder.<\/li>\n
    • Working WordPress cron, or a real server cron that calls wp-cron.php<\/code>.<\/li>\n<\/ul>\n
      Editorial note: This overview combines WordPress.org official plugin metadata with an AI-assisted LethaldiranMX editorial review. Plugin data should be verified on the official WordPress.org listing before installation.<\/div>","protected":false},"excerpt":{"rendered":"
      Schedule automatic local backups for AI1WM \/ All-in-One WP Migration and Backup with retention, logs, and admin-only backup management.<\/p>","protected":false},"author":1,"featured_media":11619,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[252],"tags":[2864,2865,869,871,2156,555],"class_list":["post-11618","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-trends","tag-ai1wm","tag-automatic-backups","tag-backup","tag-migration","tag-scheduled-backups","tag-wordpress-plugin"],"_links":{"self":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11618","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/comments?post=11618"}],"version-history":[{"count":0,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11618\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media\/11619"}],"wp:attachment":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media?parent=11618"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/categories?post=11618"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/tags?post=11618"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}