This document is intended to outline the process with which you confirm WP Remote is fully functional on a given Web Host. The primary behaviors you’ll be testing are:

  • Confirming WP Remote indicates Core, Plugins, and Themes as needing update.
  • Updating WordPress Core.
  • Updating Themes and Plugins.
  • Performing an On-Demand Backup.
  • Performing an Automatic Backup (Premium Feature)
  • Installing a Theme or Plugin with WP Remote (Premium Feature)

Human Made uses this document internally as our testing standard, so please send us suggestions if you come across them.


If you’d like to test WP Remote on a given Web Host, very first order of business is to configure WordPress installation with a variety of out of date plugins and themes. If you’re able to, install an older version of WordPress as well.

Ideally, the test WordPress install you’ve created also includes content that needs to be backed up. This includes Posts with galleries, Pages, custom tables and other data you might typically find in a WordPress install. WP Remote supports Automatic Backups up to 5 GB in size, so the more sample content you can upload, the better.


Start your test by adding the WordPress Site to your WP Remote account. WP Remote should report that it can connect to the Site, but the WP Remote Plugin isn’t installed.

Click on the link provided by WP Remote, and install the WP Remote Plugin through the WordPress admin. Use the API key provided by WP Remote on your WordPress Site.


Navigate back to WP Remote and refresh your Site. WP Remote should be able to connect to your Site, retrieve its data, and, on the first panel, show any out of date Plugins / Themes / Core. Each time a Site is refreshed, it fetches basic data about the WordPress Site, as well as checks whether Core, Themes, or Plugins are out of date.

If you were able to install an old version of WordPress on the Site, try updating WordPress Core. The update process should take less than 30 seconds and complete successfully. Once WordPress is updated successfully, an entry is logged in the Site’s History tab and WordPress Core will be removed from the Updates list.

Try updating a Plugin to the latest version. Once the Plugin is updated successfully, an entry will be logged in the Site’s History tab and the Plugin will be removed from the Updates list. WP Remote supports updating Plugins from, as well as some premium Plugins that have implemented an update mechanism.

Try updating a Theme to the latest version. Once the Theme is updated successfully, an entry will be logged in the Site’s History tab and the Theme will be removed from the Updates list.

Refresh the Site to ensure there weren’t any false positives during updates.


Once you’ve tested the update process, you can proceed to test WP Remote’s backup feature. Behind the scenes, the WP Remote Plugin uses a slightly customized version of HM Backup. It will first try to back up the Site using the “zip” command if it’s available on the server, then ZipArchive, then PclZip. For larger Sites, or Web Hosts where web requests are killed after a certain number of seconds, the WP Remote Plugin will use a “file manifest” approach to back up the Site in chunks.

Using the web interface for WP Remote, a user should be able to create a full backup of a Site using the “Download Site” button on the Backups tab. The end of the process will prompt a pop-up which includes a direct link to the backup ZIP. Download the backup ZIP, open, and confirm all of the Site’s files are included. The database SQL file should be included in the root directory.

WP Remote’s Automatic Backup process is simply daily backup task. Within a day of enabling Automatic Backups, a backup ZIP should be available for download. Download the ZIP and confirm all of the files for the Site are included.