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 release manager is preparing a staging test sheet for a live membership site.
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: A staging copy may contain real member data and send real mail.
Illustrative situation
Illustrative scenario, not a customer case study: A release manager is preparing a staging test sheet for a live membership site. Tests cover member access, forms and indexing boundary with owners.
Choose the approach
Choose representative data and exclude live-only actions in staging. 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 · Create a staging environment in xCloud
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
List change scope, expected pages and data sensitivity
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- List change scope, expected pages and data sensitivity; exact site identity, named approver and controlled sample data.
- Action
- List proposed change, protected URLs, form flows, account roles and live data that must not be copied unnecessarily.
- Expected result
- Checklist has relevant positive and negative paths.
- Verify
- Checklist has relevant positive and negative paths. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a required role lacks a test account, obtain one before release testing.
Sources: WordPress roles and capabilities · Create a staging environment in xCloud · Paid Memberships Pro initial setup and payment gateway planning
Step 2 of 5
Review staging eligibility and access
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Create eligible staging with controlled access; exact site identity, named approver and controlled sample data.
- Action
- Review staging entitlement and current site configuration in xCloud without creating or syncing it yet.
- Expected result
- The release manager knows whether staging is available.
- Verify
- The release manager knows whether staging is available. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If plan does not support staging, write a safe alternate test approach.
Sources: WordPress roles and capabilities · Create a staging environment in xCloud · Paid Memberships Pro initial setup and payment gateway planning
Step 3 of 5
Define future pull and data scope
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Select files and database pull scope in dashboard; exact site identity, named approver and controlled sample data.
- Action
- Define files/database pull scope and sensitive data handling for a future dashboard action; exclude mail/payment side effects in test environment.
- Expected result
- The proposed copy scope is explicit.
- Verify
- The proposed copy scope is explicit. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If production personal data is unnecessary, use representative synthetic data instead.
Sources: WordPress roles and capabilities · Create a staging environment in xCloud · Paid Memberships Pro initial setup and payment gateway planning
Step 4 of 5
Write role-specific positive and negative test cases
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Write role-specific positive and negative test cases; exact site identity, named approver and controlled sample data.
- Action
- Write acceptance cases for member, expired member, anonymous visitor, editor and form recipient with expected records.
- Expected result
- A tester can execute the sheet without guessing.
- Verify
- A tester can execute the sheet without guessing. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the sheet says only 'looks good', add observable states.
Sources: WordPress roles and capabilities · Create a staging environment in xCloud · Paid Memberships Pro initial setup and payment gateway planning
Step 5 of 5
Review results and production push exclusions
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Review results and production push exclusions; exact site identity, named approver and controlled sample data.
- Action
- Review production push exclusions, backup and owner approval criteria with the business owner; link to actual release procedure.
- Expected result
- The checklist protects newer live records.
- Verify
- The checklist protects newer live records. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a planned database push would overwrite members or orders, revise its scope.
Sources: WordPress roles and capabilities · Create a staging environment in xCloud · Paid Memberships Pro initial setup and payment gateway planning
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: Tests cover member access, forms and indexing boundary with owners. 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
A checklist does not create or restore staging. It must name a completed backup requirement, live-data exclusions and a separate authorized dashboard operator for a later test or release.
Create a staging environment in xCloud · Site backups in xCloud
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.
Copyable agent brief
Manual checkpoints
- The named site, business or provider owner supplies application evidence the connected hosting reads cannot observe.
- A separately approved operator performs any later configuration, staging, update, restore or publication described in the decision sheet.
- The owner accepts the review finding and proposed checks without treating the unexecuted change as completed.
Feature coverage
- business-acceptance (covered): Tests cover member access, forms and indexing boundary with owners. Write role-specific positive and negative test cases
- recovery (covered): A staging copy may contain real member data and send real mail. Review results and production push exclusions
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
- Create a staging environment in xCloud
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Paid Memberships Pro initial setup and payment gateway planning