# Promote a tested WordPress change Confirm backup, staging results, production window, and post-release checks. Production reflects the fix and post-test orders remain intact. Canonical: https://xcloud.host/use-cases/solutions/promote-a-tested-wordpress-change/ Published: 2026-09-30 · Updated: 2026-09-30 · Technical review: 2026-09-30 Evidence: Source reviewed; no production deployment test claimed Editorial owner: xCloud editorial Intent: Confirm backup, staging results, production window, and post-release checks. For: business-owner, operator ## Requirements and responsibilities - Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: An agency has approved a design fix on staging while live orders continue. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) - Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) - Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: A full database push may overwrite orders and users. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) - Before any database copy or restore starts, the authorized operator restricts the target and quarantines outbound mail, payment, fulfillment and other provider effects. Restored settings may overwrite plugin suppression; reapply sandbox credentials and verify isolation before testing. Sources: [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ## Illustrative situation Illustrative scenario, not a customer case study: An agency has approved a design fix on staging while live orders continue. Production reflects the fix and post-test orders remain intact. ## Choose the approach - Push only the selected files or tables needed by the change. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Site Security PRO setup and eligibility](https://xcloud.host/docs/set-up-site-security-pro/) - Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) ## Dashboard and application procedure ### 1. Record exact changed files, tables and live-data delta **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Record exact changed files, tables and live-data delta; exact site identity, named approver and controlled sample data. **Action:** Compare staging change log with production files, tables and orders created since last pull. Mark exactly what must move. **Expected result:** The promotion scope is smaller than an unexamined full copy. **Verify:** The promotion scope is smaller than an unexamined full copy. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If live-data delta is unknown, stop before push. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ### 2. Take fresh production backup and confirm restore point **Where:** xCloud Site Backup dashboard **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Take fresh production backup and confirm restore point; exact site identity, named approver and controlled sample data. **Action:** Confirm a fresh production files-and-database backup and access to its restore point. **Expected result:** The live site has a pre-release recovery point. **Verify:** The live site has a pre-release recovery point. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If backup fails, hold the push. Capability: Configure native WordPress backup and restore Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ### 3. Review staging push scope with store owner **Where:** xCloud Staging Management dashboard **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Review staging push scope with store owner; exact site identity, named approver and controlled sample data. **Action:** In Staging Management select only approved files or tables and review overwrite behavior with the store owner before pressing Push to Production. **Expected result:** The dashboard shows the intended scope. **Verify:** The dashboard shows the intended scope. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If the selected scope includes new order tables, cancel and redesign it. Capability: Create and synchronize WordPress staging Sources: [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ### 4. Push approved scope in xcloud staging management **Where:** xCloud Staging Management dashboard **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Push approved scope in xcloud staging management; exact site identity, named approver and controlled sample data. **Action:** Run the approved dashboard push, wait for logs to finish and record the operation; do not infer completion from MCP reads. **Expected result:** The selected change reaches production. **Verify:** The selected change reaches production. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If the job errors, inspect deployment log before retrying or restoring. Capability: Create and synchronize WordPress staging Sources: [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ### 5. Check order continuity, page rendering and indexability **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Check order continuity, page rendering and indexability; exact site identity, named approver and controlled sample data. **Action:** Check live design, checkout, newest order and production indexing; compare with pre-push order identifiers. **Expected result:** The fix is live without losing orders. **Verify:** The fix is live without losing orders. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If order continuity fails, preserve current data and begin an owner-led recovery decision. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ## Maintenance - Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: Production reflects the fix and post-test orders remain intact. A chat prompt is not a scheduled task. Sources: [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/); [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) - Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## Recovery decisions - Before restoring, compare the chosen recovery point with newer business records. A full database push may overwrite orders and users. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) ## AI handoff Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only. ### Supported scope - **Confirm requirements and inspect resources** (mcp; read): Discover the connected profile and operation schema first; only teams granted to the connection are visible. Checkpoint: Confirm exact team, server and site identity. Use dashboard\_url returned by the resource; do not invent a dashboard link. Operation identifiers to discover: teams.index, servers.show, sites.show. Scopes: read:servers, read:sites. Sources: [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - **Review a WordPress business journey** (app; manual): Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence. Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision. Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) - **Configure native WordPress backup and restore** (dashboard; manual): Native schedule, retention and destination changes and all restores are dashboard-only. Checkpoint: Use Site → Site Backup. Before restoring, confirm backup, target, scope and treatment of newer records. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - **Create and synchronize WordPress staging** (dashboard; manual): WordPress staging requires an eligible paid plan. The API staging-create operation is for Git sites. Checkpoint: Use Site overview → Add Staging and staging Site → Manage Staging. Inspect push/pull scope before overwriting data. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ### Copyable agent brief ```text Help with promote a tested wordpress change for the exact xCloud team and site I name. Read available hosting identity and state first, then ask the named WordPress, app, provider or dashboard owner for operations and records outside this connection. Prepare these authored tasks: Record exact changed files, tables and live-data delta; Take fresh production backup and confirm restore point; Review staging push scope with store owner; Push approved scope in xcloud staging management; Check order continuity, page rendering and indexability. The acceptance check is: The selected change reaches production. Do not infer application transactions or completed dashboard jobs from hosting resource reads. WordPress staging push/pull, backup schedule, restore and cache-setting changes require the authorized dashboard owner; the packaged REST wrapper is GET-only. ``` ### Manual checkpoints - The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: In Staging Management select only approved files or tables and review overwrite behavior with the store owner before pressing Push to Production. - The business owner compares the controlled sample with this observable result: The selected change reaches production. - Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only. ## Feature coverage - **business-acceptance** (covered): Production reflects the fix and post-test orders remain intact. Steps: phase-4 - **recovery** (covered): A full database push may overwrite orders and users. Steps: phase-5 ## Sources - [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) — reviewed 2026-09-30; v4.4.2 package; xCloud v2.8.8 capability review - [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) — reviewed 2026-09-30 - [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) — reviewed 2026-09-30 - [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) — reviewed 2026-09-30 - [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) — reviewed 2026-09-30 - [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/) — reviewed 2026-09-30 - [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) — reviewed 2026-09-30 - [Site Security PRO setup and eligibility](https://xcloud.host/docs/set-up-site-security-pro/) — reviewed 2026-09-30 - [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/) — reviewed 2026-09-30 - [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) — reviewed 2026-09-30 - [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/restore-a-wordpress-backup-to-another-site/) - [Release WordPress staging changes without losing live data](https://xcloud.host/use-cases/playbooks/wordpress-staging-release-with-live-data/)