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: A store manager sees updates for shipping, payment and coupon plugins.
xCloud agent capability boundaries · WordPress 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.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Bulk updating can hide which component broke checkout.
Illustrative situation
Illustrative scenario, not a customer case study: A store manager sees updates for shipping, payment and coupon plugins. Staging orders pass payment, shipping and coupon cases after selected updates.
Choose the approach
Change one connected component set at a time after compatibility review. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · xCloud WooCommerce hosting
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.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Inventory exact WooCommerce extension versions and changelogs
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Inventory exact woocommerce extension versions and changelogs; exact site identity, named approver and controlled sample data.
- Action
- List exact WooCommerce, payment, shipping and coupon plugin versions and vendor release notes; choose the smallest compatible change set.
- Expected result
- The reviewer can state which extension is being updated and why.
- Verify
- The reviewer can state which extension is being updated and why. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If vendor support or PHP compatibility is unclear, defer that extension.
Sources: WordPress roles and capabilities · WooCommerce testing orders · xCloud WooCommerce hosting
Step 2 of 5
Confirm completed backup and create eligible staging
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Confirm completed backup and create eligible staging; exact site identity, named approver and controlled sample data.
- Action
- Confirm a completed files-and-database backup and its storage access before any production-affecting update.
- Expected result
- A usable point precedes the change window.
- Verify
- A usable point precedes the change window. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the latest backup failed or excludes order data, create and verify another point first.
Sources: Site backups in xCloud · xCloud agent capability boundaries · WooCommerce testing orders · xCloud WooCommerce hosting
Step 3 of 5
Apply selected updates to staging and inspect logs
- Where
- xCloud Staging Management dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Apply selected updates to staging and inspect logs; exact site identity, named approver and controlled sample data.
- Action
- Before any production pull, restrict staging access and isolate outbound email, fulfillment and payment effects. Then use eligible xCloud staging in the dashboard, pull only approved data scope and apply selected extensions there.
- Expected result
- Staging contains the proposed versions without touching live orders.
- Verify
- Staging contains the proposed versions without touching live orders. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a pull would expose sensitive data or send real messages, adjust staging settings first.
Sources: Create a staging environment in xCloud · xCloud agent capability boundaries · WooCommerce testing orders · xCloud WooCommerce hosting
Step 4 of 5
Run payment sandbox, refund, coupon and shipping tests
- Where
- WooCommerce administrator and payment gateway sandbox
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Run payment sandbox, refund, coupon and shipping tests; exact site identity, named approver and controlled sample data.
- Action
- In gateway sandbox place orders with coupon, shipping and tax cases; inspect order status, refund path and emails in app/provider records.
- Expected result
- The changed extensions pass store-specific transaction tests.
- Verify
- The changed extensions pass store-specific transaction tests. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If one path fails, hold the production update and isolate the extension.
Sources: WooCommerce testing orders · WordPress plugin administration · xCloud WooCommerce hosting
Step 5 of 5
Approve production update and monitor live order state
- Where
- Business owner acceptance sheet and selected application records
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Approve production update and monitor live order state; exact site identity, named approver and controlled sample data.
- Action
- Write a production change request naming exact extension slugs, backup point, update window, order checks and rollback decision. Hand it to the authorized release owner; this review stops before live execution.
- Expected result
- The later production update has a concrete approval package.
- Verify
- The later production update has a concrete approval package. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If no owner accepts the order and data risks, leave the update pending.
Sources: WordPress roles and capabilities · xCloud agent capability boundaries · WooCommerce testing orders · xCloud WooCommerce hosting
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: Staging orders pass payment, shipping and coupon cases after selected updates. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · 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.
Recovery decisions
Before restoring, compare the chosen recovery point with newer business records. Bulk updating can hide which component broke checkout. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
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 and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- 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.
- 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.
- 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.
- Configure and test application behavior app · manual
xCloud hosting operations do not configure WooCommerce checkout, n8n workflows, Nextcloud sharing policy or application users.
Checkpoint: An application administrator verifies each real business journey and records observed outcomes.
WooCommerce testing orders · n8n Webhook node and test/production URLs · Nextcloud file sharing administration · xCloud agent capability boundaries
- Business owner review and acceptance app · manual
Human planning, acceptance and record reconciliation cannot be inferred from xCloud resource reads. The business owner chooses the application's source of truth.
Checkpoint: Record approved criteria, observed application evidence, unresolved questions and named follow-up.
WordPress roles and capabilities · xCloud agent capability boundaries
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Before any production pull, restrict staging access and isolate outbound email, fulfillment and payment effects. Then use eligible xCloud staging in the dashboard, pull only approved data scope and apply selected extensions there.
- The business owner compares the controlled sample with this observable result: The changed extensions pass store-specific transaction tests.
- 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): Staging orders pass payment, shipping and coupon cases after selected updates. Run payment sandbox, refund, coupon and shipping tests
- recovery (covered): Bulk updating can hide which component broke checkout. Approve production update and monitor live order state
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- xCloud MCP documentation and connection profiles
- xCloud WooCommerce hosting
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- WooCommerce testing orders
- Create a staging environment in xCloud
- n8n Webhook node and test/production URLs
- Nextcloud file sharing administration