Docs / WordPress Toolkit / Staging

WordPress Staging

Panelica 1.0.375 Verified 2026-07-23 WordPress Toolkit

Staging gives every WordPress site a safe twin: a full copy on staging.yourdomain.com where you test updates, themes and redesigns, then push to live when it works. One button creates it; nothing about DNS, vhosts, databases or URLs is left to you.

Panel locationWP Toolkit → Staginghttps://YOUR-SERVER-IP:8443/wordpress/staging

WordPress Staging · example.com

Status

Active

Files

1.8 GB

Database

142 MB

Last Sync

22.07.2026

Staging URLhttps://staging.example.com

Databasestg_example_wp

Sync from Live Push to Live Delete Staging

Creating a staging copy

Pick a site, click create, optionally leave a note. That is the whole form, because everything else is automatic: the staging subdomain (with DNS and web server configuration), a separate staging database, the file copy, and the URL rewrite of the whole site to the staging address. While it builds, the page shows a live status and polls until the copy is ready; a failed attempt offers Retry and Delete.

Behind the scenes: staging is a first-class subdomain, not a hidden folder. Files are cloned with rsync (skipping caches and VCS folders), the database is duplicated with a streamed dump into a stg_-prefixed copy, and the URL swap is a careful three-pass search-replace across all tables covering the https, http and protocol-relative forms of your domain, with the GUID column left untouched as WordPress best practice dictates. The staging copy is also flagged noindex so search engines never see your experiments, and it keeps its own wp-config so the two sites can never cross their database wires.

Working with it

Four info cards keep the state visible (status, file size, database size, last sync), a details box holds the URL, path and database, and a comparison table shows production and staging side by side. From there:

Sync from Live re-copies production onto staging: files, database, or both, your choice, with a clear warning that staging's current state is overwritten. Use it to restart an experiment from fresh production data.
Push to Live (promote) is the reverse and is treated with the respect it deserves: a danger-zone dialog where you choose files and/or database and must literally type PROMOTE before the button arms.

Behind the scenes of promote: before anything touches production, the panel takes an automatic safety backup of whatever it is about to replace: the live files, the database, or both, matching the scope you chose. Then staging's files sync over (your live wp-config is preserved), the database is cloned back, URLs are rewritten from the staging address back to the real one, search-engine visibility is switched back on and caches are flushed. If the redesign turns out to be a mistake, the pre-promote backup is your way back.

Delete Staging removes the staging subdomain, its files and its database, behind a typed destructive confirmation listing exactly those three consequences.

Workflow example: before a WooCommerce major update: Sync from Live for fresh data, run the update on staging, click through checkout and the top pages, then Push to Live with both boxes ticked. Total production risk: the length of one rsync, with a safety backup on top.

Access

Behind the wordpress license feature and scoped to your own sites by the roles and permissions chain. Staging defaults to ROOT, ADMIN and RESELLER (a plain USER does not get it unless an operator grants the page). A frozen site must be unfrozen before a staging copy can be created for it.

Panelica Documentation · Written and verified against the live panel. · Last verified 2026-07-23 on Panelica 1.0.375