# Plan PHP compatibility checks for WordPress Plan a PHP compatibility test for a plugin requirement using version evidence, a future staging matrix and a rollback criterion. Canonical: https://xcloud.host/use-cases/solutions/plan-php-compatibility-checks-for-wordpress/ 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: Inventory plugin/theme dependencies and test site behavior after any PHP change. 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: A plugin vendor requires a newer PHP version than the site currently runs. 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 PHP switch can break old themes or extensions. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) ## 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. 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/); [xCloud PHP version and settings](https://xcloud.host/docs/how-to-upgrade-php-version-with-xcloud-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. 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. 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. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud PHP version and settings](https://xcloud.host/docs/how-to-upgrade-php-version-with-xcloud-hosting/); [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/) ### 2. 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. Capability: Confirm requirements and inspect resources 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); [xCloud PHP version and settings](https://xcloud.host/docs/how-to-upgrade-php-version-with-xcloud-hosting/); [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/) ### 3. 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. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud PHP version and settings](https://xcloud.host/docs/how-to-upgrade-php-version-with-xcloud-hosting/); [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/) ### 4. 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. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud PHP version and settings](https://xcloud.host/docs/how-to-upgrade-php-version-with-xcloud-hosting/); [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/) ### 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. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud PHP version and settings](https://xcloud.host/docs/how-to-upgrade-php-version-with-xcloud-hosting/); [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-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. 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 - 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. Sources: [xCloud PHP version and settings](https://xcloud.host/docs/how-to-upgrade-php-version-with-xcloud-hosting/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## 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/) ### Copyable agent brief ```text Review plan php compatibility checks for wordpress for the exact site and team I name. Use permitted reads and ask for application evidence you cannot observe. Work through: Inventory current PHP version, WordPress version, theme, plugins and required extensions for the exact site.; Read xCloud PHP-version controls and vendor requirements for a candidate version; distinguish documented support from hope.; Draft a staging test procedure including backup, PHP dashboard setting, error logs and rollback version; do not switch PHP in this planning task.; List login, forms, checkout and scheduled jobs to check under the candidate version, with expected result and owner.; Present the compatibility decision and separate change request with exact target and rollback criteria. Return observations, uncertainties, a decision and a separately approvable operator checklist. Do not create, restore, configure, publish or update anything in this review. ``` ### 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. Steps: phase-4 - **recovery** (covered): A PHP switch can break old themes or extensions. 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 - [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) — reviewed 2026-09-30 - [xCloud PHP version and settings](https://xcloud.host/docs/how-to-upgrade-php-version-with-xcloud-hosting/) — 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 - [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/review-server-capacity-for-multiple-wordpress-sites/) - [Release WordPress staging changes without losing live data](https://xcloud.host/use-cases/playbooks/wordpress-staging-release-with-live-data/)