How staging works
Staging is a full copy of your Pressy at its own address — same content, same plugins, same theme, its own WordPress you can sign into. It does not count towards your plan and is not billed.
To make one, see create a staging site.
The two directions
| Action | What it replaces |
|---|---|
| Sync from live | Staging. Live is untouched |
| Push to live | Live. The only action in the product that replaces live content |
Both copy the whole site — files and database — and files present on the destination but absent from the source are deleted. WordPress URLs are rewritten between the two addresses automatically.
A push takes a backup of live first, and if that backup fails the push is abandoned. When it succeeds, the previous version of live is in your Backups.
The freshness line
The screen states one fact about the two copies: when they were last identical. If that was three weeks ago, a push will replace three weeks of live activity — orders, form entries, comments, uploads.
Switching the whole dashboard
One control moves every screen onto the staging copy, so you can change a PHP version or a cron job against the copy. Billing, Domains and Plan stay read-only there.
What this can’t do
Nothing compares the two copies. There is no diff — only the date they were last identical.
What to do: if that date is more than a few days old, press Sync from live to pull live down, redo your change, and push from a fresh copy.
You cannot push one page, one plugin or one file.
What to do: for a single small change, make it on live and take a backup first.
The staging address is public and search engines can find it.
What to do: do not put anything on staging you would not publish. For real privacy, add HTTP authentication with a plugin, or an IP allow-list.
Didn’t solve it?
Write to us with your Pressy’s address and what you were doing when it went wrong. Answered by the people who built it.
Last updated