Staging is a private copy for testing; it must not replace newer production orders, posts or form entries.
Steps
- Take a production backup and create a staging clone with the cPanel WordPress tool when available.
- Protect staging from public access and search indexing. Use separate payment/API test credentials.
- Apply and test the theme, plugin, PHP or code change on staging.
- Before pushing, note which files and database tables will be replaced; take another production backup.
- Push only the required scope during a quiet period, then clear caches and run critical user journeys.
Verify the result
Production must retain recent content and pass login, form, purchase and scheduled-task tests.
Important: Never copy an old staging database over a busy live site without a content-freeze and explicit recovery plan.
