Museder RestoreOne vs PatchOn Agent

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 One-click full-site backup Export the database, meta.json, and wp-content/ into a single archive you can download or restore later. Restore Center wizard A clear 3-step flow: upload & analyze → review summary & options → start restore with real-time progress and logs. Chunked uploads with validation Bypass upload_max_filesize / post_max_size limits by uploading your archive in small chunks, with retries and integrity checks. Shared-hosting friendly Uses pure PHP + WordPress APIs for database backup/restore, and falls back from ZipArchive to PclZip compression when needed. Schedules and logs Create one or more automatic backup schedules (or run backups manually), then inspect, download, or clean up structured backup and restore logs. Neo-glass admin UI Modern Dashboard, Backups, Restore, Schedules, Logs and Settings screens with clear calls-to-action, status messages, and responsive layout. 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. External services This plugin does not use external services. The only programmatic outbound HTTP the base plugin performs by default is an optional, short non-blocking request to your own site’s wp-cron.php (same host / local loopback) to encourage scheduled tasks to run. No third-party API is called for backups or restores. All admin JavaScript and CSS for RestoreOne are loaded from files shipped under this plugin’s assets/ directory (including vendored libraries under assets/vendor/). Optional add-ons, if you install them separately, may introduce their own network behavior; see each add-on’s readme. See the FAQ for more on the local wp-cron.php nudge. Privacy What this plugin stores on your server Backups — Complete-site archives are written under your WordPress uploads area (typically wp-content/uploads/museder-restoreone/backups/ or the path shown on the Backups screen). Each archive contains a database export (database.ndjson), meta.json, and a copy of wp-content/ from your site at backup time. Logs — Text logs for backup, restore, and related operations are stored under wp-content/uploads/museder-restoreone/logs/ (see the Logs admin screen). Restore reports — When you generate a restore report, files are stored under wp-content/uploads/museder-restoreone/reports/ (or the path configured for reports on your install). Schedules and settings — Options and scheduled events are stored in your WordPress database like other plugins. Diagnostics Version / build heartbeat — After an upgrade, the plugin may write a one-line informational entry to the local Logs directory (same server, no remote host) noting the active plugin version and build id. This is for support troubleshooting only. Exact folder names may vary with your uploads path or custom content directory; nothing is sent to a fixed external hostname by this plugin. The plugin resolves these locations using WordPress APIs (for example wp_upload_dir() and path helpers derived from your install) rather than hard-coded internal constants, so custom wp-content or uploads layouts can be reflected correctly where your host allows. Third parties The free plugin does not upload your backup contents, database, or logs to third-party APIs or clouds. That statement matches External services above and the FAQ entries on external data and local wp-cron loopback. Optional add-ons (separate plugins or extensions, if you install and activate them) could send specific categories of data to remote storage or services only when you enable and configure those extensions; the base RestoreOne plugin does not do that on its own. Retention and deletion You can delete backup archives from the Backups screen, remove or download logs from Logs, and adjust retention-related options where provided. Uninstall (uninstall.php) removes plugin-owned options, transients (including timeout rows), dynamic job-lock option rows, and scheduled cron hooks whose names start with museder_restoreone_. It does not delete backup ZIP archives, log files, restore reports, or other files under your uploads/storage tree; delete those manually from the Backups / Logs UI or your host if you no longer need them. On Multisite, uninstall walks sites in batches (100 IDs per query) instead of loading the entire network at once. Very large networks should still use a maintenance window so uninstall is not interrupted by web-server timeouts. Developer Development source of truth is the public GitHub repository: https://github.com/artherslin-source/museder-restoreone Contributors and release maintainers should follow the Modification & Release SOP (docs/SOP-PLUGIN-DEVELOPMENT-AND-RELEASE.md in the repo). Summary: Branching: work on fix/, feature/, or agent/ branches from current main; avoid long-lived dirty main. WordPress.org Lite: fully functional, GPL, no license gates, trialware, or bundled Add-on/PRO code in the Lite package or SVN. Security: every sensitive AJAX/REST/form handler needs capability checks, nonces, sanitize/validate input, and escaped output. Release version sync (six fields, same version): museder-restoreone.php Version, MUSEDER_RESTOREONE_VERSION, MUSEDER_RESTOREONE_BUILD_ID, readme.txt Stable tag, new Changelog block, and new Upgrade Notice block (easy to forget — WP.org shows the notice to updaters). Package Lite ZIP: use create-package.sh or tools/package-lite-windows.ps1 only; require BOUNDARY_CHECK=PASS. Do not use PowerShell Compress-Archive. Lite ZIP must not include docs/, tools/, .cursor/, .github/, logs/, or museder-restoreone-pro/. GitHub release: after explicit approval, tag vX.Y.Z on main; GitHub Actions builds release artifacts. WordPress.org SVN: commit Lite source files only (no zip); copy trunk to tags/X.Y.Z; fill docs/RELEASE-X.Y.Z-SVN-HANDOFF.md from the template before SVN commit. Checklists: docs/RELEASE_CHECKLIST.md, docs/PACKAGING.md, docs/WORDPRESS_ORG_DEVELOPMENT_GUIDE.md, AGENTS.md.

PatchOn is an AI service that runs your WordPress plugin, theme, and core updates for you. It reproduces your production site in a staging environment, lets AI verify whether each update can be applied safely, and applies only the updates that pass every check to production. If an update ever fails, one click restores your site. This plugin acts as the agent connecting your WordPress site to PatchOn. Getting Started This plugin requires the PatchOn service (patchon.jp) and does not function on its own. Activation alone performs no external communication and does not redirect you. Clicking “Start PatchOn” on the welcome screen opens a consent dialog describing the data that will be sent; confirming it with “Agree and Start” registers your site anonymously and, if updates are available, starts the first inspect-and-update run. No account is required to get started — you need one only to: view detailed inspection results configure automatic updates use paid features Main Features Pre-inspection — in a staging environment, AI compares before / after screenshots of your site to detect layout breakage and fatal errors Inspect and update — a manual run goes from inspection to production rollout in one action, applying only updates that passed every check Automatic updates with inspection — the site is inspected on a schedule and only updates that passed every check are applied Backups — taken automatically right before each update and downloadable for a plan-based retention period One-click restore — if an applied update fails, one click puts your site back to the pre-update backup This plugin (the free distribution on WordPress.org) does not write patched code to your site files, even when it detects a problem. AI auto-repair, which fixes the code causing a problem found during a pre-inspection, is provided by the separately distributed PatchOn Agent Pro extension plugin (available to paid plan subscribers). This plugin writes to your site files in only two cases: applying the updates themselves through the standard WordPress upgrader, and the one-click restore, which runs only on your explicit request and writes your own backed-up plugins, themes, MU plugins, and wp-content drop-ins (and your database) back to the site. Data Sent Once you have consented on the consent screen, running a “Pre-inspection” or “Apply update” sends the following data to PatchOn and related external services. See the Privacy Policy for details. Site URL / WordPress version / PHP version / DB version List and versions of installed plugins, themes, and MU plugins List of available updates (names and versions of plugins, themes, and WordPress core). While the site is connected, this is sent automatically once a day Site files prior to update application, used for the pre-update backup: wp-config.php, active and to-be-updated plugins and themes, MU plugins, and wp-content drop-ins (such as object-cache.php) Contents of WordPress debug.log (used to detect issues) A full copy of your site’s database, taken during a pre-inspection and reused as the pre-update backup. It may include personal data stored on your site, such as member accounts or contact-form submissions External services This plugin depends on the following external services. No external communication is performed merely by activating the plugin; it starts only after you explicitly click the “Agree and Start” button on the consent screen shown on first use. PatchOn API (https://patchon.jp and its subdomains) The backend for all inspection, repair, update, and database-dump operations. Two host names are used, both operated by Rocketa Inc. and routed to PatchOn’s infrastructure: https://patchon.jp/api/* — site registration, pre-inspection control, apply-update control, billing https://dump.patchon.jp/* — database-dump control endpoints and signed-URL chunk uploads for pre-inspections and pre-update backups Provider: Rocketa Inc. (rocketa.co.jp) When data is sent: On click of the “Agree and Start” consent button (one-time): anonymous site registration and UUID issuance Once a day while connected (daily check-in): the list of available updates and plugin version When the user runs a “Pre-inspection”, or when automatic updates run their scheduled inspection: list of plugins / themes, debug.log, full database copy When the user runs an “Apply update”, or when automatic updates apply an update that passed every check: a backup (site files and a full database copy) and the application result When the user runs the one-click restore after a failed update: restore control requests and progress status (the backed-up files and database themselves are downloaded from cloud storage at that time, not sent) What is sent: see the “Data Sent” section above Terms of Service: https://patchon.jp/terms Privacy Policy: https://patchon.jp/privacy-policy Subprocessors: https://patchon.jp/subprocessors AWS S3 (Tokyo region, accessed via PatchOn) Storage destination for the site backup (zip) and the database copy (uploaded in chunks). Uploads and downloads are performed only against pre-signed URLs issued by PatchOn on a per-request basis. The customer site does not hold any S3 credentials. During a one-click restore, the backed-up site files and database chunks are downloaded from S3 in the same way. Provider: Amazon Web Services, Inc. Endpoint: https://*.s3.ap-northeast-1.amazonaws.com (pre-signed URLs only) When data is sent: when the user runs a “Pre-inspection” (database copy) or an “Apply update” (backup: site files and database copy) What is sent: site files (zip) and a full copy of the database AWS Privacy: https://aws.amazon.com/privacy/