Skip to main content
Print

Working on Your Staging Site

This guide explains how to open your staging site, what its sandbox blocks, and what differs from your live site.

Before you start

  • You have a staging site whose status is Completed (see Creating a Staging Site).
  • You know the username and password you use on your live site.

Opening the staging site

  1. On your live site, go to Hera Backup > Staging Sites.
  2. Find your staging site, click Actions in its row, and choose Open. The staging site opens in a new tab. You can also click its address in the URL column.
  3. Sign in with the same username and password you use on the live site. The staging site keeps its own login cookies, so you sign in to it separately even while you are signed in on the live site.

Open stays unavailable while the copy is still being made, and on a staging site whose copy was cancelled or failed.

You can also go to the staging site's admin directly:

  • Subfolder: https://yoursite.com/staging-{slug}/wp-admin/ (the path is the one you chose on the wizard's Name step)
  • Subdomain (Pro): https://staging.yoursite.com/wp-admin/, using the host name you entered

How to tell you are on the staging site

  • The WordPress admin bar shows an orange STAGING badge, in the admin and on the front of the site.
  • The admin bar also carries a Push staging changes to live link, which opens the live site's push page for this staging site. Pushing needs Pro; see Pushing Changes to Live.
  • Hera Backup's own screens on the staging site show a Staging environment. notice: scheduled backup runs, license checks and Hub uploads are switched off there, and real backups are managed on the live site.

The sandbox

Every staging site runs in a sandbox, on Free and on Pro. It is installed when the copy is made, and there is no switch for it in the interface.

  • Email: mail sent through WordPress (wp_mail), such as order notifications and password resets, is not delivered.
  • Scheduled tasks: WP-Cron runs none of the events copied from the live site (scheduled posts among them), only Hera Backup's own, and the staging copy of wp-config.php sets DISABLE_WP_CRON unless your wp-config.php already sets it. Action Scheduler runs no jobs, so WooCommerce order processing and subscription renewals do not happen, and WooCommerce webhooks are not delivered.
  • Outbound requests: requests made through WordPress's HTTP API go nowhere except to the staging site itself and to localhost, because the copy holds your live site's API keys. Each blocked host is noted in the staging site's Hera Backup log. A developer can allow a host with the hera_backup/staging/allowed_hosts filter. A plugin that opens its own network connections instead of using WordPress's HTTP API is not stopped by this rule.
  • Search engines: every page carries a noindex, nofollow robots meta tag, robots.txt disallows everything, and WordPress reports the site as not public, so search engines are asked to ignore the copy.

What you can do on staging

Most of what you do in WordPress: edit content, change settings, adjust WooCommerce products and configuration, switch or customise your theme, and activate, deactivate or delete plugins.

Installing or updating a plugin or theme from WordPress.org is an outbound request, so the sandbox blocks it. Uploading a plugin or theme as a ZIP file does not need one.

What differs from live

Area Live Staging
Outgoing email Sent Not delivered
WP-Cron and Action Scheduler Run Do not run
Outbound HTTP requests (WordPress's HTTP API) Allowed Blocked, except to the staging site itself
Search indexing As you set it Discouraged (noindex, robots.txt)
Admin bar Standard Shows the STAGING badge
Payment gateways Live Switch to test mode yourself

A payment gateway that talks to its servers through WordPress's HTTP API cannot reach them from the staging site, unless a developer allows its host with the filter above. A gateway that opens its own connection is not stopped by the sandbox, so put your payment gateways in test mode on the staging site before you try a checkout there.

Getting changes to live

Nothing on the staging site reaches your live site until you push it. Pushing changes back is a Pro feature: see Pushing Changes to Live.

Table of Contents