View Categories

Using Loupely on a Staging Site

2 min read

Loupely works on staging sites #

The Loupely WordPress Plugin can be installed on a staging site the same way it’s installed on a live site. Staging is actually one of the most valuable places to use it. You can trigger failures intentionally, run diagnoses on them, and understand what’s breaking before anything reaches your live environment. The plugin generates its own connection key per installation, so your staging site has a separate key from your live site.

Two connections, two keys #

If you want to diagnose both your staging and live sites from the same Chrome extension, you need the connection key from each. When you’re browsing the staging domain, enter the staging site’s key in the extension. When you’re on the live domain, use the live key. The extension detects which site you’re on by URL, but the key has to match the installation on that specific site.

Practically: keep both keys somewhere you can copy them quickly. The staging plugin settings page in the staging admin shows the staging key. The live plugin settings page shows the live key.

Diagnosis credits and staging #

Diagnoses on a staging site consume credits the same as diagnoses on a live site. Credits are account-level, not environment-specific. If you run a lot of exploratory diagnoses during development and want to preserve credits for production use, be intentional about when you trigger a full diagnosis on staging versus just reviewing the capture file, which is always free.

Common staging-specific behavior #

Staging sites sometimes behave differently than live sites in ways that affect Loupely’s output. If your staging environment uses a different PHP version than production, PHP Errors that don’t exist on the live site will appear in staging captures, and vice versa. If the staging database is a copy of production that was taken weeks ago, WooCommerce pipeline captures may reflect order patterns that don’t match your current live state. Neither of these is a Loupely problem. They’re the normal limitations of staging environments that don’t perfectly mirror production. The captures are still accurate for the environment they’re taken from.