{"id":405694,"date":"2026-11-20T04:27:22","date_gmt":"2026-11-20T04:27:22","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/backuppilot\/"},"modified":"2026-11-20T04:26:53","modified_gmt":"2026-11-20T04:26:53","slug":"wrensafe","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/wrensafe\/","author":18413741,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.1.6","stable_tag":"1.1.6","tested":"7.1.5","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"Wrensafe \u2013 Backup, Restore & Migration","header_author":"Husnain Gohar","header_description":"Back up, restore and migrate WordPress with confidence: full or partial backups, encryption, schedules, staging, rollback, and restores of backups made by other plugins.","last_updated":"2026-11-20 04:26:53","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/profiles.wordpress.org\/oyegohar\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":43,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.1.6":{"tag":"1.1.6","author":"oyegohar","date":"2026-11-20 04:26:53","revision":3812913}},"upgrade_notice":{"1.1.6":"<p>Security hardening for restores of TAR backups and of backup SQL. Recommended for everyone.<\/p>","1.1.5":"<p>Fixes backups that could miss database rows on busy sites. Recommended for everyone.<\/p>","1.1.4":"<p>Security and reliability fixes, WordPress 6.2 or later required. SFTP off-site copies are no longer included; choose FTP\/FTPS or S3-compatible storage instead.<\/p>","1.1.3":"<p>Direct Migration no longer stops with &quot;Too many requests&quot;, continues an interrupted transfer, and explains HTTPS and key problems before sending. Update both sites.<\/p>","1.1.2":"<p>If uploading a new version added a second Wrensafe instead of replacing it, Wrensafe now shows why and how to fix it once; deleting a duplicate copy always keeps your data.<\/p>","1.1.1":"<p>The new Wrensafe look: new logo and menu icon, Cobalt Ice colours and Manrope headings. The backup progress window also shows the check and the off-site copy steps.<\/p>","1.1.0":"<p>Adds off-site copies to FTP, SFTP and S3-compatible storage, a separate database schedule, table and large-file exclusions, automatic backup checks, Search &amp; Replace, Site Health checks and a Dashboard widget.<\/p>","1.0.3":"<p>Fixes hosting malware scanners (such as SiteGround&#039;s) wrongly flagging the security scan file, and stops storing staging passwords.<\/p>","1.0.2":"<p>New name: Wrensafe. Your settings and backups carry over, and the backup folder moves to wp-content\/wrensafe-storage automatically.<\/p>","1.0.1":"<p>Backups no longer contain wp-config.php or the site&#039;s security keys, and sites with custom folder locations are backed up and restored completely.<\/p>","1.0.0":"<p>First stable release of Wrensafe.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.gif":{"filename":"icon-128x128.gif","revision":3812901,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.gif":{"filename":"icon-256x256.gif","revision":3812901,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3812901,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3812901,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3812901,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.6"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3812901,"resolution":"1","location":"assets","locale":"","width":1440,"height":1080},"screenshot-10.png":{"filename":"screenshot-10.png","revision":3812901,"resolution":"10","location":"assets","locale":"","width":1440,"height":1150},"screenshot-11.png":{"filename":"screenshot-11.png","revision":3812901,"resolution":"11","location":"assets","locale":"","width":1440,"height":1471},"screenshot-12.png":{"filename":"screenshot-12.png","revision":3812901,"resolution":"12","location":"assets","locale":"","width":1440,"height":1632},"screenshot-13.png":{"filename":"screenshot-13.png","revision":3812901,"resolution":"13","location":"assets","locale":"","width":1440,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3812901,"resolution":"2","location":"assets","locale":"","width":1440,"height":900},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3812901,"resolution":"3","location":"assets","locale":"","width":1440,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3812901,"resolution":"4","location":"assets","locale":"","width":1440,"height":1000},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3812901,"resolution":"5","location":"assets","locale":"","width":1440,"height":900},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3812901,"resolution":"6","location":"assets","locale":"","width":1440,"height":900},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3812901,"resolution":"7","location":"assets","locale":"","width":1440,"height":1611},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3812901,"resolution":"8","location":"assets","locale":"","width":1440,"height":1150},"screenshot-9.png":{"filename":"screenshot-9.png","revision":3812901,"resolution":"9","location":"assets","locale":"","width":1440,"height":1000}},"screenshots":{"1":"Dashboard: see at a glance whether your site is backed up, plus recent backups, schedules and migration readiness.","2":"Back up the whole site, or only the database, files, media, themes or plugins, with optional AES-256 encryption.","3":"Every backup shows live, step-by-step progress and can be cancelled safely.","4":"Backup Browser: restore, download, verify, lock, tag and delete the backups stored on your server.","5":"Review before you restore: where the backup comes from, what's inside, what will change, and which parts to restore.","6":"Integrity verification checks the archive, manifest, database files and checksums before you restore.","7":"Automatic backups: the whole site and the database on separate schedules, keeping only the newest copies.","8":"Migration Assistant scores how ready the site is to move, recommends the safest method and lists the next steps.","9":"Settings grouped by task: the backup folder, backups before updates, exclusions, notifications, migration and WooCommerce Safe Mode.","10":"Restore backups made by other backup plugins: upload the files just as that plugin saved them.","11":"Off-site copies: copy each backup to FTP\/FTPS or S3-compatible storage, and test the connection before saving.","12":"Search &amp; Replace: a dry run shows how many rows would change in each table before anything is saved.","13":"The Dashboard widget: the newest backup, the next scheduled one, the off-site copy, and Back up now."}},"plugin_section":[262246],"plugin_tags":[151,2814,4155,152,19979],"plugin_category":[59],"plugin_contributors":[294096],"plugin_business_model":[],"class_list":["post-405694","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-backup","plugin_tags-clone","plugin_tags-migration","plugin_tags-restore","plugin_tags-staging","plugin_category-utilities-and-tools","plugin_contributors-oyegohar","plugin_committers-oyegohar"],"banners":{"banner":"https:\/\/ps.w.org\/wrensafe\/assets\/banner-772x250.png?rev=3812901","banner_2x":"https:\/\/ps.w.org\/wrensafe\/assets\/banner-1544x500.png?rev=3812901","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/wrensafe\/assets\/icon.svg?rev=3812901","icon":"https:\/\/ps.w.org\/wrensafe\/assets\/icon.svg?rev=3812901","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-1.png?rev=3812901","caption":"Dashboard: see at a glance whether your site is backed up, plus recent backups, schedules and migration readiness."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-2.png?rev=3812901","caption":"Back up the whole site, or only the database, files, media, themes or plugins, with optional AES-256 encryption."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-3.png?rev=3812901","caption":"Every backup shows live, step-by-step progress and can be cancelled safely."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-4.png?rev=3812901","caption":"Backup Browser: restore, download, verify, lock, tag and delete the backups stored on your server."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-5.png?rev=3812901","caption":"Review before you restore: where the backup comes from, what's inside, what will change, and which parts to restore."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-6.png?rev=3812901","caption":"Integrity verification checks the archive, manifest, database files and checksums before you restore."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-7.png?rev=3812901","caption":"Automatic backups: the whole site and the database on separate schedules, keeping only the newest copies."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-8.png?rev=3812901","caption":"Migration Assistant scores how ready the site is to move, recommends the safest method and lists the next steps."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-9.png?rev=3812901","caption":"Settings grouped by task: the backup folder, backups before updates, exclusions, notifications, migration and WooCommerce Safe Mode."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-10.png?rev=3812901","caption":"Restore backups made by other backup plugins: upload the files just as that plugin saved them."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-11.png?rev=3812901","caption":"Off-site copies: copy each backup to FTP\/FTPS or S3-compatible storage, and test the connection before saving."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-12.png?rev=3812901","caption":"Search &amp; Replace: a dry run shows how many rows would change in each table before anything is saved."},{"src":"https:\/\/ps.w.org\/wrensafe\/assets\/screenshot-13.png?rev=3812901","caption":"The Dashboard widget: the newest backup, the next scheduled one, the off-site copy, and Back up now."}],"raw_content":"<!--section=description-->\n<p>Wrensafe backs up your WordPress site and restores it \u2014 on the same server or on a completely different one \u2014 without guesswork. Every backup is a single <code>.wbp<\/code> archive with its own manifest and checksums, every restore starts with an integrity check, and the dashboard tells you plainly whether your site is protected.<\/p>\n\n<h3>Back up<\/h3>\n\n<ul>\n<li><strong>Full site or just what you need:<\/strong> database, files, media, themes, plugins, or everything.<\/li>\n<li><strong>AES-256 encryption<\/strong> (optional, per backup). The password is never stored.<\/li>\n<li><strong>Automatic backups<\/strong> every day, week or month at the time you choose, keeping only the newest copies \u2014 with a separate schedule for the database, for example the database every day and the whole site every week. Plus an automatic safety backup before WordPress, plugin or theme updates.<\/li>\n<li><strong>Off-site copies:<\/strong> each backup can be copied to your own FTP\/FTPS or S3-compatible storage right after it's made. It's sent in small parts that resume after an interruption, so large backups work on any host, and only the newest copies are kept there. Passwords and keys are stored encrypted.<\/li>\n<li><strong>Checked after every backup<\/strong> (optional): the same integrity check as Verify runs as soon as a backup is made, and a backup that fails it is reported instead of being kept as good.<\/li>\n<li><strong>No size limits:<\/strong> multi-gigabyte sites back up, download, upload and restore. Interrupted downloads and uploads resume where they stopped.<\/li>\n<li><strong>Works on shared hosting:<\/strong> backups and restores run in small, time-limited steps, so they finish even where PHP may only run for 30 seconds.<\/li>\n<li><strong>Smart exclusions:<\/strong> other plugins' backup archives and cache folders are skipped by default; plugin and theme code is always backed up completely. You can also leave out files larger than a size you choose, and database tables you don't need, such as large log or statistics tables.<\/li>\n<\/ul>\n\n<h3>Restore safely<\/h3>\n\n<ul>\n<li><strong>Integrity first:<\/strong> the archive, manifest, database and file checksums are verified before anything changes.<\/li>\n<li><strong>Rollback points:<\/strong> a safety backup is created automatically before every restore, so a restore can be undone.<\/li>\n<li><strong>Atomic database swap:<\/strong> the database is rebuilt in temporary tables and switched over in one step, so your site keeps working during the import.<\/li>\n<li><strong>Restore what you need:<\/strong> the whole site, only the database, only the files, or just the media, themes or plugins.<\/li>\n<li><strong>Your server settings stay yours:<\/strong> <code>wp-config.php<\/code> is never put in a backup or overwritten, so your database password and security keys stay on the server. Wrensafe itself is never overwritten, and server-specific files (<code>.htaccess<\/code>, <code>.user.ini<\/code>, cache drop-ins) are kept when you move a site to another server.<\/li>\n<li><strong>Plugin safety:<\/strong> after a restore, Wrensafe loads the site once. Any plugin that is incomplete, needs a newer PHP or WordPress than this server has, or stops the site from loading is turned off instead of breaking the site, and you're told which one and why.<\/li>\n<li><strong>WooCommerce Safe Mode<\/strong> keeps new orders, customers and stock untouched while the rest of the store is restored.<\/li>\n<\/ul>\n\n<h3>Migrate<\/h3>\n\n<ul>\n<li><strong>Move a site to a new domain or server:<\/strong> upload a <code>.wbp<\/code> archive on the new site; URLs and file paths are rewritten safely, including inside serialized data and page-builder JSON. Different table prefixes are handled automatically.<\/li>\n<li><strong>Direct Migration:<\/strong> send a backup straight to another WordPress site using a one-time migration key \u2014 no download or upload. It arrives in that site's backup list, ready to review and restore.<\/li>\n<li><strong>Migration Assistant:<\/strong> scans your server limits, database and files, and recommends the safest way to migrate.<\/li>\n<li><strong>Staging:<\/strong> create a password-protected copy of your site, test changes, then push them to live.<\/li>\n<li><strong>Search &amp; Replace:<\/strong> change text anywhere in the database \u2014 for example an old address \u2014 safely inside serialized and JSON data. A dry run shows how many rows would change before anything is saved.<\/li>\n<\/ul>\n\n<h3>Switch from another backup plugin<\/h3>\n\n<ul>\n<li><strong>Restore backups made by other plugins:<\/strong> upload a backup from All-in-One WP Migration (<code>.wpress<\/code>), UpdraftPlus, Duplicator, WPvivid, BackWPup, Backup Migration, Total Upkeep, Solid Backups (BackupBuddy), WP Migrate or Jetpack VaultPress Backup under <strong>Import \/ Restore \u2192 Other Backup Plugins<\/strong>. Wrensafe reads it, shows what's inside and restores it with the same checks as its own backups. The other plugin doesn't need to be installed.<\/li>\n<li><strong>Any other backup:<\/strong> a <code>.sql<\/code> database dump and\/or a <code>.zip<\/code> or <code>.tar<\/code> of the <code>wp-content<\/code> folder works too, for example from your hosting control panel.<\/li>\n<li>Backups split over several files (UpdraftPlus, WPvivid) are uploaded together; each file resumes if the connection drops.<\/li>\n<\/ul>\n\n<h3>Stay informed<\/h3>\n\n<ul>\n<li><strong>Dashboard:<\/strong> protection status, recent backups, schedules and migration readiness at a glance.<\/li>\n<li><strong>Activity Logs<\/strong> that record every step with the exact reason when something fails (passwords and keys are never logged), plus a one-click debug bundle for support.<\/li>\n<li><strong>Email notifications<\/strong> when a backup or restore fails, and, if you like, when one completes.<\/li>\n<li><strong>Site Health checks:<\/strong> Tools \u2192 Site Health tells you when the newest backup is out of date, when backups are only on this server, and when the backup folder can be downloaded from the web.<\/li>\n<li><strong>Dashboard widget:<\/strong> the newest backup, the next scheduled one and the off-site copy status on the WordPress Dashboard, with a Back up now button.<\/li>\n<\/ul>\n\n<h3>Credits<\/h3>\n\n<p>Wrensafe includes the Manrope typeface by The Manrope Project Authors (github.com\/googlefonts\/manrope), licensed under the SIL Open Font License 1.1; the licence is in <code>assets\/admin\/fonts\/OFL.txt<\/code>.<\/p>\n\n<h3>Privacy<\/h3>\n\n<p>Wrensafe stores backups on your own server and never sends them, or any usage data, to Wrensafe. Data leaves your site only when an administrator sets up or starts one of the features listed under External services, such as copying backups to their own remote storage. Backups can contain personal data (user accounts, orders, form entries), so download and store them as carefully as the site itself.<\/p>\n\n<h3>External services<\/h3>\n\n<p>Wrensafe only contacts the services below, and only after a site administrator configures or starts the related feature (the Site Health check, which only calls the site itself, is the one exception). Nothing is sent on activation, and no usage data or tracking is collected. Like every request WordPress makes, these requests include the site's address in the User-Agent header.<\/p>\n\n<ul>\n<li><strong>WordPress.org core checksums API<\/strong> (api.wordpress.org) \u2014 when an administrator runs the Security scan (Wrensafe \u2192 System Info), to compare WordPress core files with the official checksums. Data sent: the site's WordPress version. <a href=\"https:\/\/wordpress.org\/about\/privacy\/\">Privacy Policy<\/a>.<\/li>\n<li><strong>Import from URL<\/strong> \u2014 downloads a backup archive from the URL the administrator enters on the Import \/ Restore page. Nothing is sent to that server apart from the request itself.<\/li>\n<li><strong>Direct Migration<\/strong> \u2014 when an administrator sends a backup, sends it to the other WordPress site they pair with a one-time migration key, and only to that site. Data sent: the migration key, the backup archive (in signed parts), its file name, size, type and checksum, and this site's address, which is shown in the receiving site's backup list.<\/li>\n<li><strong>Remote storage<\/strong> \u2014 when an administrator sets it up under Settings \u2192 Remote storage, backup archives are uploaded to the FTP\/FTPS or S3-compatible server they enter, using the login or keys they enter. Wrensafe also lists and deletes older copies in that folder or bucket to keep only the newest ones. Which service this is, and its terms and privacy policy, are the administrator's choice: no service is preset (the providers named in the settings are only examples), and Wrensafe has no service of its own.<\/li>\n<li><strong>Site Health check of the backup folder<\/strong> \u2014 requests a short test file from the site's own address, to check that backups can't be downloaded from the web. It runs when Tools \u2192 Site Health is opened and during WordPress's own weekly Site Health check. No other server is contacted.<\/li>\n<li><strong>Email notifications<\/strong> \u2014 backup, restore and copy results are sent with WordPress's own <code>wp_mail()<\/code> to the addresses set under Settings \u2192 Notifications, through whatever mail service the site uses.<\/li>\n<\/ul>\n\n<!--section=installation-->\n<ol>\n<li>In your WordPress admin, go to <strong>Plugins \u2192 Add New Plugin<\/strong>, search for <strong>Wrensafe<\/strong>, then select <strong>Install Now<\/strong> and <strong>Activate<\/strong>. (Or upload the <code>wrensafe<\/code> folder to <code>\/wp-content\/plugins\/<\/code> and activate it on the <strong>Plugins<\/strong> screen.)<\/li>\n<li>Open <strong>Wrensafe<\/strong> in the admin menu.<\/li>\n<li>Click <strong>Create backup<\/strong> to make your first full backup.<\/li>\n<li>Optional: turn on automatic backups under <strong>Scheduled Backups<\/strong>.<\/li>\n<\/ol>\n\n<p>To move a site: create a full backup on the old site, download it from the <strong>Backup Browser<\/strong>, install Wrensafe on the new site and upload the file under <strong>Import \/ Restore<\/strong>.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"where%20are%20my%20backups%20stored%3F\"><h3>Where are my backups stored?<\/h3><\/dt>\n<dd><p>On your own server, in <code>wp-content\/wrensafe-storage\/<\/code> by default. You can choose another folder under <strong>Settings \u2192 Backup \u2192 Backup folder<\/strong>; a folder outside the website folder is safest, and existing backups move with it. Folders inside the website are protected from direct web access. Download a copy now and then and keep it somewhere safe, away from the server.<\/p><\/dd>\n<dt id=\"can%20backups%20be%20copied%20to%20another%20server%20or%20to%20cloud%20storage%3F\"><h3>Can backups be copied to another server or to cloud storage?<\/h3><\/dt>\n<dd><p>Yes. Under <strong>Settings \u2192 Remote storage<\/strong>, choose FTP\/FTPS or S3-compatible storage (Amazon S3 or any service with an S3-compatible API), enter the details and select <strong>Test connection<\/strong>. Each automatic backup, and optionally each backup you make yourself, is copied there right after it's made, and only the newest copies you choose to keep are left there. FTP needs PHP's FTP extension (most hosts have it). If a copy fails, the backup stays on your server, the Backup Browser shows it, and you get an email if failure emails are on.<\/p><\/dd>\n<dt id=\"how%20do%20i%20change%20my%20site%27s%20address%20in%20the%20database%3F\"><h3>How do I change my site's address in the database?<\/h3><\/dt>\n<dd><p>Open <strong>Wrensafe \u2192 Search &amp; Replace<\/strong>, enter the old address and the new one, and start a dry run: it shows how many rows in each table would change, without saving anything. Then select <strong>Replace now<\/strong>. Serialized data and JSON stay valid, and post GUIDs are left as they are unless you choose otherwise. Make a database backup first: a replacement can only be undone by restoring one.<\/p><\/dd>\n<dt id=\"is%20wp-config.php%20in%20my%20backups%3F\"><h3>Is wp-config.php in my backups?<\/h3><\/dt>\n<dd><p>No. <code>wp-config.php<\/code> holds your database password and the security keys and salts that sign logins, so it is never put in a backup, downloaded or sent to another site. The keys WordPress can keep in the database are left out too. A restore always keeps the destination site's own <code>wp-config.php<\/code> and keys.<\/p><\/dd>\n<dt id=\"my%20site%20keeps%20wp-content%20%28or%20plugins%2C%20or%20uploads%29%20in%20another%20folder.%20is%20that%20backed%20up%3F\"><h3>My site keeps wp-content (or plugins, or uploads) in another folder. Is that backed up?<\/h3><\/dt>\n<dd><p>Yes. Wrensafe asks WordPress where each folder is, so content, plugins, must-use plugins, themes and uploads are backed up wherever they are, and restored into the matching folders of the destination site, even when its layout is different.<\/p><\/dd>\n<dt id=\"what%20is%20a%20.wbp%20file%3F\"><h3>What is a .wbp file?<\/h3><\/dt>\n<dd><p>Wrensafe's backup archive. It is a ZIP container (TAR on servers without the ZIP extension) with a manifest, metadata, per-table database files and checksums, so a restore can check every part before using it. Encrypted backups are wrapped in AES-256.<\/p><\/dd>\n<dt id=\"can%20i%20restore%20a%20backup%20onto%20a%20different%20site%20or%20domain%3F\"><h3>Can I restore a backup onto a different site or domain?<\/h3><\/dt>\n<dd><p>Yes. Upload the <code>.wbp<\/code> file under <strong>Import \/ Restore<\/strong> on the new site. Wrensafe keeps the new site's own domain, <code>wp-config.php<\/code> and server files, and rewrites the old URLs and paths in the database for you.<\/p><\/dd>\n<dt id=\"can%20i%20restore%20a%20backup%20made%20by%20another%20backup%20plugin%3F\"><h3>Can I restore a backup made by another backup plugin?<\/h3><\/dt>\n<dd><p>Yes, without installing that plugin. Go to <strong>Import \/ Restore \u2192 Other Backup Plugins<\/strong> and upload the backup files:<\/p>\n\n<ul>\n<li>All-in-One WP Migration: the <code>.wpress<\/code> file.<\/li>\n<li>UpdraftPlus: every file of one backup (the <code>-db.gz<\/code> file and the <code>-plugins<\/code>, <code>-themes<\/code>, <code>-uploads<\/code> and <code>-others<\/code> zips).<\/li>\n<li>Duplicator: the <code>_archive.zip<\/code> or <code>_archive.daf<\/code> file (<code>installer.php<\/code> isn't needed).<\/li>\n<li>WPvivid: the <code>_backup_all.zip<\/code> file, or every part of one backup.<\/li>\n<li>BackWPup: the <code>.zip<\/code>, <code>.tar<\/code> or <code>.tar.gz<\/code> archive.<\/li>\n<li>Backup Migration: the <code>BM_\u2026.zip<\/code> file.<\/li>\n<li>Total Upkeep: the <code>boldgrid-backup-\u2026.zip<\/code> file of a full backup.<\/li>\n<li>Solid Backups (BackupBuddy): the <code>.zip<\/code> file of a full backup.<\/li>\n<li>WP Migrate: a full-site export <code>.zip<\/code>, or a database export (<code>.sql<\/code> or <code>.sql.gz<\/code>).<\/li>\n<li>Jetpack VaultPress Backup: the <code>.tar.gz<\/code> backup download.<\/li>\n<\/ul>\n\n<p>Password-protected backups from other plugins can't be read; make an unencrypted backup in that plugin first. WordPress core files are not restored (this site keeps its own), only <code>wp-content<\/code> and the database.<\/p><\/dd>\n<dt id=\"will%20restoring%20log%20me%20out%3F\"><h3>Will restoring log me out?<\/h3><\/dt>\n<dd><p>A database restore replaces the users table with the one from the backup, so you will be asked to log in again at the end \u2014 with the usernames and passwords from the site the backup came from.<\/p><\/dd>\n<dt id=\"does%20it%20work%20on%20shared%20hosting%3F\"><h3>Does it work on shared hosting?<\/h3><\/dt>\n<dd><p>Yes. Backups, restores, uploads and verification all run in short, time-limited steps, so they complete even where PHP may only run for 30 seconds.<\/p><\/dd>\n<dt id=\"can%20it%20handle%20large%20sites%3F\"><h3>Can it handle large sites?<\/h3><\/dt>\n<dd><p>Yes. There is no size limit. A 2.4 GB site (25,000 files, 30,000 posts) was backed up, downloaded, uploaded to another site and restored on a server limited to 30-second requests and 8 MB uploads, with every file and database row checked afterwards. You need free disk space about equal to your site's size to create a backup, and about one and a half times the backup's size to restore one. Interrupted downloads and uploads resume where they stopped.<\/p><\/dd>\n<dt id=\"is%20encryption%20optional%3F\"><h3>Is encryption optional?<\/h3><\/dt>\n<dd><p>Yes. Turn it on per backup. The password is never stored or logged \u2014 keep it safe, because a lost password cannot be recovered.<\/p><\/dd>\n<dt id=\"does%20it%20work%20with%20woocommerce%3F\"><h3>Does it work with WooCommerce?<\/h3><\/dt>\n<dd><p>Yes. WooCommerce Safe Mode protects orders, customers and stock during a restore, and the checkout is paused only while the store's data is being replaced.<\/p><\/dd>\n<dt id=\"does%20it%20support%20multisite%3F\"><h3>Does it support multisite?<\/h3><\/dt>\n<dd><p>Not yet. Wrensafe is built and tested for single-site WordPress. Restoring a multisite database is blocked to protect the network.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20uninstall%20the%20plugin%3F\"><h3>What happens when I uninstall the plugin?<\/h3><\/dt>\n<dd><p>Nothing is deleted unless you turn on <strong>Settings \u2192 Advanced \u2192 Uninstall<\/strong>. Even then, only Wrensafe's settings and records are removed from the database \u2014 your backup files are always kept.<\/p><\/dd>\n<dt id=\"what%20are%20the%20minimum%20requirements%3F\"><h3>What are the minimum requirements?<\/h3><\/dt>\n<dd><p>WordPress 6.2 or later and PHP 7.4 or later (PHP 8.3 or newer is recommended). Tested up to WordPress 7.1 and PHP 8.4. The PHP ZIP extension is recommended.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.1.6<\/h4>\n\n<ul>\n<li>Security: a TAR backup is checked before PHP opens it, so a crafted file can no longer make PHP 7 create objects from data hidden in the archive. Wrensafe's own TAR backups (made where ZipArchive is missing) open as before.<\/li>\n<li>Security: a restore now refuses SQL statements that would copy another table, a file on the server or another server's data into the table being restored (subqueries, LOAD_FILE, MERGE\/FEDERATED\/CONNECT tables, CREATE TABLE \u2026 LIKE, variables). Backups made by Wrensafe and the supported plugins restore as before.<\/li>\n<li>Fixed: restoring a TAR backup (made on a server without ZipArchive) restored only the database and none of the site's files, while reporting success. It restores the files now.<\/li>\n<li>Changed: removed two unused nonce helpers.<\/li>\n<li>Changed: External services in this readme now say exactly what Direct Migration sends, and where the security scan is.<\/li>\n<\/ul>\n\n<h4>1.1.5<\/h4>\n\n<ul>\n<li>Fixed: a backup could miss database rows when the site deleted others while the backup ran (for example WordPress removing its ping notes for new posts, or expired sessions). Tables are now read in the order of their primary key, so rows deleted during a backup no longer make it skip rows that still exist.<\/li>\n<\/ul>\n\n<h4>1.1.4<\/h4>\n\n<ul>\n<li>Changed: the plugin is now called \"Wrensafe \u2013 Backup, Restore &amp; Migration\".<\/li>\n<li>Changed: Wrensafe now needs WordPress 6.2 or later (PHP 7.4 or later, as before). On an older WordPress or PHP it stays inactive and says what it needs instead of stopping the site.<\/li>\n<li>Changed: off-site copies go to FTP\/FTPS or S3-compatible storage. SFTP is no longer included: its connection relied on a PHP feature many hosts block. Saved SFTP settings are kept and Settings \u2192 Remote storage explains what to do.<\/li>\n<li>Security: Direct Migration's receiving site now checks the key, the request limits and every field before it accepts a request, and \"Restrict to one IP address\" now locks the key to the first server that sends with it, as described.<\/li>\n<li>Security: temporary database files made during a backup, restore or import now have names that can't be guessed, and the storage folder is protected on Apache 2.2 and 2.4 (without errors) and on IIS.<\/li>\n<li>Security: settings saved by any route are checked like the Settings screen checks them, a backup can only be deleted from the backup folders, Import from URL no longer reaches addresses on the server's own network, and on multisite only network administrators can use Wrensafe.<\/li>\n<li>Security: a restore only runs the table statements of the backup it restores; anything else stops the restore before the live site changes.<\/li>\n<li>Fixed: \"Push to live\" copied the staging site's own Wrensafe records and its address and \"discourage search engines\" setting to the live site.<\/li>\n<li>Fixed: backups included the tables of staging sites, so each new staging site copied the earlier ones.<\/li>\n<li>Fixed: a restore's clean-up could remove the temporary tables of another WordPress site that shares the database.<\/li>\n<li>Fixed: the safety file a restore uses stayed behind when Wrensafe was deactivated during a restore, which could leave the site blank; it is now removed on deactivation and can't be opened directly.<\/li>\n<li>Fixed: migration keys expired early on sites ahead of UTC, and a key could expire during a long transfer.<\/li>\n<li>Fixed: a remote storage password with a backslash didn't work after saving.<\/li>\n<li>Fixed: a missing Zip, Zlib, bz2 or OpenSSL extension now gives a clear message instead of an error; backup encryption is turned off with the reason when OpenSSL is missing.<\/li>\n<li>Fixed: some error messages showed a character code instead of an apostrophe or a quote.<\/li>\n<li>Changed: emails are sent as plain text; Wrensafe's menu icon styles load only for users who see the menu; WordPress's own notices are no longer moved on Wrensafe's screens; the 5-minute background check runs only while a schedule is on (otherwise once a day).<\/li>\n<\/ul>\n\n<h4>1.1.3<\/h4>\n\n<ul>\n<li>Fixed: Direct Migration stopped with \"Too many requests\" partway through a larger backup, and new attempts were refused too. The receiving site no longer counts the parts of a transfer that uses a valid key, its limits no longer extend themselves while you retry, and the sending site waits and continues when asked to slow down (also with a receiving site on an older version).<\/li>\n<li>Fixed: starting a transfer again with the same key now continues where it stopped instead of starting over, and short connection problems are retried automatically.<\/li>\n<li>Changed: before sending, Wrensafe checks the receiving site: that it can be reached, the key is valid, and it accepts this connection (HTTP or HTTPS). Problems are shown as an error that names the site to change, for example which site's \"Require HTTPS\" setting blocks the transfer, an address that redirects to another one, or a local site's self-made HTTPS certificate.<\/li>\n<li>Fixed: an error during Direct Migration was shown as a plain status line, and some lost their reason (\"An error occurred\").<\/li>\n<li>Changed: the Wrensafe icon in the admin menu is now the colour logo (on a small white tile while the item is open or hovered, so it stays clear on any colour scheme).<\/li>\n<\/ul>\n\n<h4>1.1.2<\/h4>\n\n<ul>\n<li>Fixed: a Wrensafe zip installed from a folder with another name (for example GitHub's \"Source code\" download, which unpacks to \"wrensafe-plugin-1.1.0\") was added as a second plugin when you uploaded a new version, instead of replacing the installed one. Wrensafe now says when it runs from such a folder and how to fix it once.<\/li>\n<li>Fixed: when two copies are active, the notice now says which version is running and has a button to deactivate the older copy.<\/li>\n<li>Fixed: deleting one copy of Wrensafe while another is still installed never removes the shared settings and backup records, even when Settings \u2192 Advanced \u2192 Uninstall is on.<\/li>\n<\/ul>\n\n<h4>1.1.1<\/h4>\n\n<ul>\n<li>Changed: the new Wrensafe look (Cobalt Ice). The new logo in each page header and the welcome tour, the Wrensafe icon in the admin menu (it follows your admin colour scheme), the brand's cobalt, navy and ice-blue colours, a light frost background on Wrensafe's pages, and the Manrope typeface for headings. Manrope is bundled with the plugin; nothing is loaded from other sites.<\/li>\n<li>Changed: new WordPress.org banner, icon and screenshots.<\/li>\n<li>Fixed: the backup progress window now lists \"Checking the backup\" and the off-site copy as their own steps when they're turned on, and its percentage no longer steps back during the check.<\/li>\n<li>Fixed: the Backup Browser count in the admin menu no longer wraps onto a second line.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>New: off-site copies (Settings \u2192 Remote storage). Each backup can be copied to FTP\/FTPS, SFTP or S3-compatible storage right after it's made, in parts that resume after an interruption, keeping only the newest copies there. Choose whether automatic backups, backups you make yourself, or both are copied. Passwords and keys are stored encrypted with the site's own security keys. The Backup Browser shows each backup's copy status, and a failed copy is emailed when failure emails are on.<\/li>\n<li>New: a separate schedule for the database, next to the full-site schedule, on the Scheduled Backups page.<\/li>\n<li>New: leave chosen database tables out of backups (Settings \u2192 Backup \u2192 Exclusions). WordPress's own tables are always backed up, and a left-out table keeps its current version when you restore.<\/li>\n<li>New: leave out files larger than a size you set. Plugin and theme files are always backed up.<\/li>\n<li>New: check each backup right after it's made (Settings \u2192 Backup \u2192 Checks). A backup that fails the check is marked damaged, isn't copied off-site, and is reported.<\/li>\n<li>New: Search &amp; Replace page with a dry run, for serialized and JSON data too. Post GUIDs are left alone by default.<\/li>\n<li>New: Site Health checks for a recent backup, off-site copies and a private backup folder, and a Wrensafe section under Site Health \u2192 Info.<\/li>\n<li>New: Dashboard widget with the newest backup, the next scheduled one, the off-site copy status and Back up now.<\/li>\n<\/ul>\n\n<h4>1.0.3<\/h4>\n\n<ul>\n<li>Fixed: some hosting malware scanners (SiteGround's among them) reported a file of the security scan as malicious, because it listed the PHP function names that malware uses, and could suspend the site. The security scan no longer keeps such a list; it now looks for long encoded payloads in PHP files instead. Nothing in the plugin matches common malware signatures (checked with ClamAV, Linux Malware Detect and PHP Malware Finder).<\/li>\n<li>Security: the staging site password is no longer stored in the database (only its hash, in the staging site's <code>.htpasswd<\/code>), and passwords kept by earlier versions are removed. The hash now uses a random salt.<\/li>\n<li>Security: settings read from a backup during a restore can't create PHP objects.<\/li>\n<li>Changed: an import from a URL stops downloading at the size limit instead of after the whole file.<\/li>\n<\/ul>\n\n<h4>1.0.2<\/h4>\n\n<ul>\n<li>New name: Wrensafe (slug <code>wrensafe<\/code>). Settings, backups and the backup list carry over, and the backup folder moves to <code>wp-content\/wrensafe-storage\/<\/code> automatically.<\/li>\n<li>Fixed: after a site had no visitors for a few days, automatic backups stayed \"overdue\" and ran again on each check until they caught up. Missed runs are now skipped, and daily, weekly and monthly backups always run at the time you set.<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Security: <code>wp-config.php<\/code> (and any copy of it) is no longer included in backups, so the database password and the authentication keys and salts are never stored in a backup, downloaded or sent by Direct Migration. The keys and salts WordPress can keep in the database are left out of backups too, and a restore keeps the destination site's own.<\/li>\n<li>Security: staging sites get their own new authentication keys and salts.<\/li>\n<li>Fixed: when <code>wp-config.php<\/code> sets the table prefix through a function (for example Docker's <code>getenv_docker()<\/code>), a staging site ran on the live site's database tables. The staging copy now always gets its own prefix, or is not created.<\/li>\n<li>Fixed: sites that keep wp-content, plugins, must-use plugins, themes or uploads outside the WordPress folder are now backed up completely, and every file is restored into the matching folder of the destination site, whatever its layout.<\/li>\n<li>Fixed: after restoring a backup from another site, the URL and path rewrite also changed Wrensafe's own backup list, so existing backups could point at folders that don't exist. Only the restored tables are rewritten now, and the WordPress folder path is matched as a whole folder.<\/li>\n<li>Changed: every folder location comes from WordPress (<code>WP_PLUGIN_DIR<\/code>, <code>WPMU_PLUGIN_DIR<\/code>, <code>get_theme_root()<\/code>, <code>wp_upload_dir()<\/code>, <code>WPINC<\/code>) instead of assumed paths.<\/li>\n<li>Fixed: staging copies skipped plugin folders named \"cache\" (only the page cache folder is skipped now), and a new staging site no longer includes copies of other staging sites. The Staging page explains when a site's folder layout can't be copied.<\/li>\n<li>Changed: Settings and Import \/ Restore name the site's real content folder instead of assuming \"wp-content\".<\/li>\n<li>Changed: the \"plugins were turned off after your restore\" notice shows on the Dashboard, the Plugins screen and Wrensafe's pages only.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First stable release.<\/li>\n<li>Removed: the beta notice and the \"Beta\" label in Wrensafe's header.<\/li>\n<\/ul>\n\n<h4>Earlier versions<\/h4>\n\n<ul>\n<li>Test releases before the first stable version.<\/li>\n<\/ul>","raw_excerpt":"Back up, restore and migrate WordPress: full or partial backups, off-site copies (FTP, S3), schedules, staging and guided restores.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/405694","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=405694"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/oyegohar"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=405694"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=405694"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=405694"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=405694"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=405694"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=405694"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}