Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Museder RestoreOne

开发者 artherslin
更新时间 2026年6月3日 17:57
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

backup migration restore database-backup site-backup

下载

2.7.276 2.7.264 2.7.263 2.7.268 2.7.271 2.7.265 2.7.273

详情介绍:

Museder RestoreOne lets you create complete WordPress backups (database + wp-content) as a single archive, and restore them in a guided 3-step wizard. It is designed for shared hosting environments and uses WordPress APIs for database backup/restore, with archive compression handled by ZipArchive or WordPress’ bundled PclZip. Key features Multisite This release is not formally tested on WordPress Multisite. For predictable results, use RestoreOne on standard single-site installs (one site per admin context). If you run a network, treat use as experimental until you have verified backups and restores on a staging clone.

安装:

  1. Upload the museder-restoreone folder (or ZIP) to the /wp-content/plugins/ directory via FTP or through the “Upload Plugin” screen in your WordPress admin.
  2. Activate the plugin through the “Plugins” menu in WordPress.
  3. Go to the Museder RestoreOne menu in your admin sidebar.
  4. Open the Backups or Restore page and create your first backup.

屏幕截图:

  • Backups page showing available backups and the backup progress bar.
  • Restore Center 3-step wizard: upload & analyze, review options, execute restore.
  • Schedules page listing upcoming backup jobs and quick schedule builder.
  • Logs page with log file list and preview panel.
  • Settings page with general options and system diagnostics.

升级注意事项:

2.7.276 Fixes Exit Safe Mode failing with a generic error after restore when DB import breaks admin-ajax session or overwrites the restore HMAC secret in uploads. This release preserves runtime auth files across the file stage, adds a nopriv Safe Mode exit path with post-complete token grants, and hardens completion overlay job/token binding. Strongly recommended if restore completes but Exit Safe Mode shows “An unexpected error occurred.” 2.7.275 Fixes Restore Step 3 on shared hosts where admin-ajax and wp-login interim-login return 403 after DB import: the UI now converges to “Restore Completed” via REST-only polling, query-style REST fallback, and read-only AJAX final-status fallback even when /wp-json becomes stale or returns HTML. This update also restores resume token continuity after page reload, keeps the completion token available until Safe Mode exit succeeds, aligns Step 3 button gating with overwrite preconditions, pins reauth redirects back to Restore page, adds post-restore safe-mode-exit auth fallback, suppresses late auth-check 403 modals, preserves destination permalink/rewrite policy across import, stabilizes restore-token verification across wp-config.php salt changes, fixes long-running restores that could show 100% while still stuck on “Waiting for action,” and hardens prefix migration against duplicate-key failures. Strongly recommended if Step 3 shows 403 errors while the backend restore actually succeeds. 2.7.274 Fixes full-site restores that could break wp-admin with a critical error when core file extraction was interrupted mid-slice, and improves Step 3 success recovery when shared hosts block admin-ajax/auth-check polling or cancel confirmation. Strongly recommended before restoring over live WordPress core on shared hosting. 2.7.273 Fixes large-site backups that never finish after ZipArchive packing completes (false verify failure → hours-long PclZip repack). Recommended if backups stall near 100% on shared hosting. 2.7.272 Fixes Backup Auto mode staying on Balanced with Smart Exclude Off when the site shows “Large site detected” (>1 GB). Recommended if Auto backup does not switch to Fast on large sites. 2.7.271 Fixes Restore Step 3 UI resetting during active jobs; recommended if you reload the restore page mid-restore. Also keeps wp-config unchanged on files-only restores and improves large-backup file-stage progress accuracy. 2.7.270 Fixes Restore Step 1 showing “Analysis failed” after a successful chunk upload on sites that need “Overwrite existing data” in Step 2. Recommended if large backup analysis completes but the wizard stays failed with an empty summary. 2.7.269 Fixes Restore Step 1 on large server backups (Load Info timeout and stale summary after analysis). Recommended if 500MB+ backups fail at Step 1 or require a page reload to unlock Step 2. 2.7.268 Improves large-site restore reliability: progress polling survives session loss via restore token, nopriv progress handlers, and post-complete read grant. Recommended for long restores on production sites. 2.7.267 Adds restore site profile detection, preflight warnings, restore order/scope/wp-config options, and bootstrap support for empty document roots. Recommended before full-site restores on existing or fresh installs. 2.7.262 Fixes large-site backup jobs that could appear stuck near 95% after a failed post-close verification (PclZip repack conflicting with an open ZipArchive handle). Recommended if you run large full-site backups on production. 2.7.261 No behavior change intended for production sites; this release mainly adds reviewer-oriented automation in the development repository (endpoint matrices, nginx+Apache smoke, ZIP install check, Multisite uninstall verification, mail/PHPCS tooling) and readme↔admin UI mapping for manual checks. 2.7.260 Stricter REST chunk session ids; safer chunk/WPress paths; neutral MusederRestoreOneAddon global (Pro alias retained); dark-theme CSS selector fix; batched Multisite uninstall. 2.7.259 Path-boundary hardening for helpers and download handlers; neutral add-on/“AI” admin copy; uninstall.php for clean option/cron removal without deleting your backups; functional-test helpers in the development repository. 2.7.258 Tightens backup-path directory prefix checks; Multisite admin notice; expanded FAQ for chunk uploads, PclZip, cron/mail, and large restores; optional functional-test tooling in the development repository. 2.7.257 UI contrast fixes for dark theme on Settings and dashboard status badges; readme schedule wording aligned with optional schedules; legacy unused restore template removed. 2.7.256 Further reduces review risk around path determination: segmented core admin include path resolution, a documented override filter for non-standard layouts, and FAQ guidance for custom language / mu-plugin paths. 2.7.255 Addresses WordPress.org feedback on determining plugin/content directories correctly: no ABSPATH-based core includes, no WP_LANG_DIR / WPMU_PLUGIN_DIR in backup scope; centralized core include helper with graceful failures. Recommended before resubmitting to the Plugin Directory. 2.7.254 REST nonce handling aligned across Chunk, AI, and v2 restore; readme adds Privacy and Multisite statements; directory index sentinels. Recommended before WordPress.org resubmission. 2.7.253 Loads PclZip from WordPress core (no bundled duplicate library); readme clarifies dev-only paths. Recommended before running full Plugin Check ruleset or resubmitting to WordPress.org. 2.7.252 Plugin Check–clean report download handling, regression test script escaping, and Docker exclude for .DS_Store. Recommended before resubmitting Plugin Check results. 2.7.251 Plugin Check / escaping fix for report download wp_die() status handling. Recommended update before WordPress.org Plugin Check resubmission. 2.7.250 Tighter NDJSON import table policy, safer AI recommendations hook, REST nonce checks aligned with AI routes. Recommended update before directory resubmission. 2.7.249 Stricter admin AJAX nonce refresh, AI scan response without quota fields, safe mode copy aligned with actual behavior. Recommended before WordPress.org resubmission. 2.7.248 Review-driven fixes: visible prefixed option keys for job locks, unlimited local schedules, backup labels for everyone, safer log download nonce order. Recommended before resubmitting to WordPress.org. 2.7.247 Security and directory-review hardening: clearer nonce checks in AJAX handlers, safer backup download order, working admin report download handler. Recommended update before WordPress.org resubmission. 2.7.246 UI polish: better dark-theme contrast on Restore Center and related cards; clearer restore progress label. Recommended update for admin readability. 2.7.245 Readme and review polish: unified changelog, FAQ for local wp-cron loopback, code formatting and AI REST namespace alignment. Update recommended before WordPress.org resubmission. 2.7.21 Security & compliance: Hardened security with comprehensive nonce verification, input sanitization, and WordPress.org standards compliance. Fixed Restore History timestamp accuracy and restore success detection. Update recommended for all users. 2.7.20 Critical fixes: Enhanced file path validation for restore operations, fixed Restore History timestamp accuracy, improved security with wp_delete_file(). Update recommended for all users. 2.7.19 Bug fixes: Fixed restore file path errors and download white screen issue. Removed hardcoded timezone offsets - all time displays now respect WordPress timezone settings. Update recommended if experiencing restore or download issues. 2.7.18 Timezone fix: All time displays now correctly use WordPress local timezone. Restore History, Dashboard, Logs, and Schedules pages now show accurate local times. Update recommended if timestamps are incorrect. 2.7.17 Code quality and security improvements: Fixed remaining AlternativeFunctions errors, enhanced NonceVerification and ValidatedSanitizedInput fixes. Improved tool recognition for phpcs comments. Update recommended for better WordPress Plugin Check compliance.

常见问题:

What does the backup archive contain?

Each backup archive includes:

  • database.ndjson — a structured export of your WordPress database (plugin-owned format).
  • meta.json — metadata about when and how the backup was created.
  • wp-content/ — your themes, plugins, and uploads.
Together, these files are enough to recreate your site on the same or another server.

Does compatibility with third-party backup formats imply an official partnership?

No. RestoreOne may document or implement technical compatibility with certain third-party archive or migration formats so you can move data between tools on your own server. That compatibility is not an endorsement, partnership, or affiliation with those projects unless explicitly stated elsewhere by the authors.

Are there any file size limits?

Yes. For safety and compatibility, single files larger than 2GB are skipped during backup. This means they will not be included in the backup ZIP and will not be restored. Sites larger than 2GB in total size can still be backed up and restored successfully as long as each individual file is smaller than 2GB. When files are skipped, the backup completion message shows the skip reasons and examples.

What happens if mysqldump is not available?

Museder RestoreOne does not require mysqldump. Database backup/restore is implemented in pure PHP using WordPress database APIs.

What if ZipArchive is not enabled on my server?

If your server does not have the ZipArchive PHP extension, the plugin will automatically use WordPress’ built-in PclZip library to create and extract archives. PclZip can be slower and more memory- or disk-sensitive on very large sites than ZipArchive. If a host blocks reading WordPress core’s wp-admin/includes/class-pclzip.php (for example via open_basedir), backup or restore may fail with a clear error in Logs — use the museder_restoreone_core_admin_include_path filter if your layout is non-standard (see FAQ below).

How does chunked restore upload work over REST?

Large archive uploads use the plugin’s authenticated REST API (museder-restoreone/v2). Chunk bytes are streamed from the HTTP request body (php://input) only for that request, assembled into temporary files under your WordPress uploads area, and never forwarded to third-party URLs. Multipart uploads use PHP’s normal uploaded-file handling instead. All chunk routes require manage_options and a valid REST nonce.

Will scheduled backups and email always run?

Scheduled backups depend on WordPress cron (or your host’s system cron if DISABLE_WP_CRON is enabled). Email notifications depend on your server’s wp_mail configuration (SMTP plugin, host mail relay, etc.). If cron or mail is blocked, use Settings → Send Test Email, check Logs, and configure host cron / mail as needed.

Can I run a full restore (execute) on a very large archive?

Very large restores may hit PHP time limits, web server timeouts, or disk space constraints on shared hosting. The Restore wizard supports validate and dry run steps so you can verify an archive before a full execute. For huge sites, prefer a staging clone or WP-CLI-driven restore where your host allows long-running PHP.

Where are the logs stored?

All logs are stored under: wp-content/uploads/museder-restoreone/logs/ You can view or download the latest logs directly from the Logs page in the Museder RestoreOne admin menu.

What happens to plugins during restore?

Optional safe mode (chosen in the Restore screen) saves a snapshot of the active plugin list and sets an admin notice so you can verify the site before clearing the marker. RestoreOne does not automatically deactivate or reactivate other plugins; you manage plugins in WordPress as usual. Exit Safe Mode only clears the marker and the stored snapshot.

Does this plugin send data to external services?

No. This plugin runs entirely on your server and does not send backup contents or site data to any external API or cloud service as part of the free base plugin. The Offline readiness / local rules scan on the Dashboard uses local heuristics only (no remote AI service is invoked by the shipped free build).

Does the plugin make HTTP requests to my own site?

Sometimes. To help scheduled tasks run promptly, the plugin may send a short, non-blocking HTTP request to your own site's wp-cron.php (a local loopback). That stays on your server, does not transmit backup contents to third parties, and is a common WordPress pattern. If DISABLE_WP_CRON is enabled, your host may rely on system cron instead.

Does this plugin expose my backup files publicly?

No. Backup download and upload endpoints are protected by time-limited tokens and secret keys generated inside your WordPress site. Only users with access to your WordPress admin can generate valid links, and each link expires after a short period of time.

Does Museder RestoreOne support WordPress Multisite?

Not as a formally supported configuration in this release. The plugin is built and QA’d primarily for single-site WordPress. Multisite networks may behave differently across subsites, uploads paths, and roles; use on Multisite only after your own testing on a staging copy of the network.

Can I use a custom languages directory?

Yes, advanced sites can override the detected languages directory with the museder_restoreone_languages_dir filter. Return an absolute path without a trailing slash, or return an empty string to skip language-directory handling.

Can I use a custom mu-plugins directory?

Yes, advanced sites can override the detected must-use plugins directory with the museder_restoreone_mu_plugins_dir filter. Return an absolute path without a trailing slash, or return an empty string if your site does not use a must-use plugins directory.

What if my WordPress core admin include files are in a non-standard location?

Most sites do not need any changes. For unusual server layouts where core admin API files cannot be found automatically, developers can use the museder_restoreone_core_admin_include_path filter to return a readable absolute path for the requested core file. Invalid or unreadable values are ignored and the plugin falls back to its default resolution.

更新日志:

2.7.276 2.7.275 2.7.274 2.7.273 2.7.272 2.7.271 2.7.270 2.7.269 2.7.268 2.7.267 2.7.262 2.7.261 2.7.260 2.7.259 2.7.258 2.7.257 2.7.256 2.7.255 2.7.254 2.7.253 2.7.252 2.7.251 2.7.250 2.7.249 2.7.248 2.7.247 2.7.246 2.7.245 2.7.244 2.7.243 2.7.242 2.7.223 2.7.220 2.7.218 2.7.17 2.7.16 2.7.15 2.7.14 2.7.13 2.7.12 2.7.11 2.7.10 2.7.09 2.7.08 2.7.07 2.7.06 2.7.05 2.7.04 2.7.03 2.7.02 2.7.01 2.6.126 2.6.125 2.6.124 2.6.123 2.6.122 2.6.121 2.6.120 2.6.119 2.6.118 2.6.117 2.6.116