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 plugin vendor requires a newer PHP version than the site currently runs.
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 PHP switch can break old themes or extensions.
Illustrative situation
Illustrative scenario: a plugin vendor requires a newer PHP version. The maintainer reviews version evidence and writes a future staging test matrix before changing any environment.
Choose the approach
Test version compatibility on staging before changing production PHP. 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 PHP version and settings
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 PHP version, plugins, theme and extensions
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Inventory php version, plugins, theme and extensions; exact site identity, named approver and controlled sample data.
- Action
- Inventory current PHP version, WordPress version, theme, plugins and required extensions for the exact site.
- Expected result
- Compatibility matrix has actual versions.
- Verify
- Compatibility matrix has actual versions. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If an extension cannot be identified, inspect the application before planning a switch.
Sources: WordPress roles and capabilities · xCloud PHP version and settings · Create a staging environment in xCloud
Step 2 of 5
Read vendor requirements and xcloud PHP controls
- Where
- xCloud team/site resource read and planning sheet
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Read vendor requirements and xcloud php controls; exact site identity, named approver and controlled sample data.
- Action
- Read xCloud PHP-version controls and vendor requirements for a candidate version; distinguish documented support from hope.
- Expected result
- The target version has a reason.
- Verify
- The target version has a reason. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a critical plugin lacks support, defer production change.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · xCloud PHP version and settings · Create a staging environment in xCloud
Step 3 of 5
Draft a future staging PHP experiment
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Create staging and change php there in dashboard; exact site identity, named approver and controlled sample data.
- Action
- Draft a staging test procedure including backup, PHP dashboard setting, error logs and rollback version; do not switch PHP in this planning task.
- Expected result
- The operator has an explicit safe experiment.
- Verify
- The operator has an explicit safe experiment. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If staging is unavailable, define an alternate test target and maintenance window.
Sources: WordPress roles and capabilities · xCloud PHP version and settings · Create a staging environment in xCloud
Step 4 of 5
Define business test cases
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Test login, forms, checkout and scheduled jobs; exact site identity, named approver and controlled sample data.
- Action
- List login, forms, checkout and scheduled jobs to check under the candidate version, with expected result and owner.
- Expected result
- The test sheet covers the site's critical PHP paths.
- Verify
- The test sheet covers the site's critical PHP paths. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If no one can test a job, retain the old version until coverage exists.
Sources: WordPress roles and capabilities · xCloud PHP version and settings · Create a staging environment in xCloud
Step 5 of 5
Request a separate production decision
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Approve production switch with backup and rollback window; exact site identity, named approver and controlled sample data.
- Action
- Present the compatibility decision and separate change request with exact target and rollback criteria.
- Expected result
- Production remains unchanged until approved execution.
- Verify
- Production remains unchanged until approved execution. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If evidence is mixed, ask the plugin vendor or run a test on a copy.
Sources: WordPress roles and capabilities · xCloud PHP version and settings · Create a staging environment in xCloud
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: Critical pages and scheduled jobs work with the target PHP version. 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
This review does not change production settings. Keep the original measurements and configuration, then write a separately approved experiment and rollback criterion before any cache, PHP or capacity change.
xCloud PHP version and settings · xCloud agent capability boundaries
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): Critical pages and scheduled jobs work with the target PHP version. Define business test cases
- recovery (covered): A PHP switch can break old themes or extensions. Request a separate production decision
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 PHP version and settings
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Create a staging environment in xCloud