Staging

A private copy of the site. Try updates and changes here first, then push them to Live when they are safe.

Staging3 changes ahead

staging-twc48628.wpv2.neoapp.id

WordPress: 7.1.4
Theme: Twenty Twenty-Five 1.5
Plugins: 15
Copied from Live: 10 Nov 09:14
Who can see it: Only your team, behind a password. Hidden from search engines.

+214 files−38 files

3 database tables

LiveRunning

twc48628.wpv2.neoapp.id

WordPress: 7.1.4
Theme: Extendable 2.2.0
Plugins: 14
Changed since the copy: 6 new comments
Who can see it: Everyone

Visit Live

What is different on staging

Compared with Live a minute ago

Theme changed to Twenty Twenty-Five 1.5

Live uses Extendable 2.2.0

Files

Plugin added: WPForms

Not installed on Live. No known vulnerabilities.

Files

2 pages edited, 1 menu changed

Database tables: posts, postmeta, options

Database

Live has 6 new comments since the copy. They are kept if you push files only, or only the tables you pick.

Push to Live

FilesThemes, plugins and uploads Database, selected tablesposts, postmeta, options. Comments and orders on Live are kept. Save a restore point of Live firstAlways on, so a push can be undone. Scan staging for vulnerabilities firstStops the push if something unsafe is found.

Visitors keep seeing the current site until the push finishes, usually under a minute.

Let staging protect Live

Try plugin and theme updates on staging first

Updates are installed on staging overnight. If its pages still look right, the same updates go to Live the next night.

Off

Restore a backup to staging

Look at an older version of the site without touching Live.

Choose a restore point

History

When	What happened	Who	Result	Actions
10 Nov 09:14	Staging created from Live	You	Done
2 Nov 14:02	Files pushed to Live, 62 files changed	You	Done