--- title: "PHP upgrades for real estate WordPress websites" description: "Choose a supported PHP target with your host, test website dependencies, and require rollback and inquiry evidence. Review the complete handoff." canonical: "https://scalewithsearch.com/articles/agent-wordpress-php-upgrade-scope" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # PHP upgrades for real estate WordPress websites: define the scope Commission a PHP upgrade as a hosting change with a named target, compatibility checks, and a recovery plan. Require evidence from the actual website before accepting it. PHP is part of the software WordPress runs on. WordPress says available PHP versions depend on the host. Updating WordPress and changing PHP are separate tasks. [WordPress PHP guidance, checked 2026.10.22](https://wordpress.org/support/update-php/). Use the questions below to define work with your host and website maintainer. The proposed tests are editorial recommendations. This guide does not establish that your particular website supports a target version. ## What does a PHP upgrade change? It changes the server runtime used by the website. WordPress directs owners to the host's settings or support for that change. Ask the maintainer to identify the affected website and hosting environment before scheduling the work. [Where PHP is changed, checked 2026.10.22](https://wordpress.org/support/update-php/). ## Is a PHP upgrade the same as a WordPress update? Scope them separately. WordPress's PHP guide calls for reviewing WordPress, themes, and plugins before changing PHP. Require an inventory of prerequisite updates and their results. Do not let a completed application update stand in for proof of the runtime change. [Preparation for PHP changes, checked 2026.10.22](https://wordpress.org/support/update-php/). ## How should the current PHP version be confirmed? Ask for a dated record from the actual website. WordPress documents the PHP version under Tools, Site Health, Info, Server. Have the host confirm which runtime serves the public site when its control panel shows other environments. [Finding the current runtime, checked 2026.10.22](https://wordpress.org/support/update-php/). ## What PHP version does WordPress currently recommend? WordPress currently recommends PHP 8.3 or greater. Treat that as a platform recommendation, then check your installed software and host. It does not certify the compatibility of every plugin on your website. [WordPress hosting requirements, checked 2026.10.22](https://wordpress.org/about/requirements/). ## Does a recommended version still need lifecycle checking? Yes. Check its support period against the PHP project's current table. The table distinguishes active support from security-only support. Ask the maintainer to include the target branch's support position in the proposal. [PHP support categories, checked 2026.10.22](https://www.php.net/supported-versions.php). ## Why should the target include an exact release? Require a specific host-supported target rather than the phrase latest PHP. Record the version used in testing and the version proposed for production. Ask who will maintain that runtime after the upgrade and whether the host controls later changes. ## What is the near-term issue with PHP 8.2? Its published security-support end date is 2026.12.31. If the maintainer proposes it as a destination, ask how the next supported move will be handled. Avoid treating a short remaining support window as an indefinite solution. [PHP branch support dates, checked 2026.10.22](https://www.php.net/supported-versions.php). ## Should the newest available branch always be selected? Choose from supported branches that the host and installed components can support. Ask for the evidence behind the selection. Keep an unknown custom integration or unsupported plugin visible instead of assuming a newer branch resolves its compatibility. ## Which website components need compatibility review? Request WordPress, the theme and child theme, page builder, form tools, listing integrations, custom plugins, and scheduled jobs. Record versions and supplier evidence. Ask the maintainer to distinguish documented support from behavior observed only in a test. ## Can a minimum requirement prove full compatibility? No. Elementor's requirements distinguish its minimum PHP version from its recommended version. Use each supplier's documentation as an input, then test the assembled website. Record any unverified extension rather than approving the entire stack from a minimum alone. [Elementor runtime requirements, checked 2026.10.22](https://elementor.com/help/requirements/). ## Can a compatibility scanner replace testing? Do not accept a scan as the whole acceptance record. WordPress's PHP guide warns that a compatibility checker can miss issues or report false positives. Require the maintainer to investigate findings and repeat the website's important tasks. [Compatibility-checker limitations, checked 2026.10.22](https://wordpress.org/support/update-php/). ## How should custom code be handled? Ask the developer to identify who maintains each customization and whether it has been tested on the target. Require a repair estimate for an actual failure. Leave undocumented custom behavior unresolved until someone can inspect and reproduce it. ## What should the test environment reproduce? Request the intended PHP target, necessary extensions, application versions, and relevant configuration. Ask the host to explain any difference from production. Keep outbound messages inside controlled test destinations while the maintainer exercises forms and scheduled work. ## Which pages should be tested? Require representative page types and the exact tasks affected by the change. Include a biography, seller service page, content article, search page when used, and form. Test editing and saving as well as public viewing. ## What should happen to PHP errors during testing? Ask the maintainer to inspect errors without exposing diagnostic output to visitors. WordPress documents separate logging and display controls and advises against debugging on live sites. Keep the relevant error and its resolution with the test record. [WordPress debugging guidance, checked 2026.10.22](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/). ## What counts as a successful inquiry test? Require the matching controlled request at its intended destination with usable question and reply details. A page that loads does not answer this acceptance question. Have the recipient verify the message and keep the receipt with the runtime test. ## What must the backup and rollback plan include? Require the website backup and host confirmation that the previous runtime can be restored. WordPress notes that reverting a backup also needs the host to move PHP back. Ask whether the host will still offer that option during the change window. [PHP recovery preparation, checked 2026.10.22](https://wordpress.org/support/update-php/). ## Should rollback restore the database automatically? Require the maintainer to explain which recovery action is needed for the observed failure. Preserve newer inquiries and content before any older database restore. Keep runtime reversal and database restoration as separately justified actions in the recovery plan. ## Who should authorize the production change? Name the business approver, host contact, and technical maintainer. State who can stop the work and invoke recovery. Require the approved target and test result before the host changes the public website's runtime. ## What should be checked after the host switches PHP? Confirm the live runtime and repeat the agreed visitor and editing tasks. Review the corresponding error evidence. Require a matching authorized inquiry receipt. Keep any mismatch between the tested and live environment open until explained. ## What should the completion record contain? Keep the previous and new runtime, host confirmation, component inventory, compatibility findings, test results, and recovery plan. Record any exclusions and their owners. A control-panel screenshot alone is insufficient for the acceptance standard proposed here. ## When does the upgrade need a wider repair scope? Request a separate proposal when a component must be replaced or a page rebuilt. Keep the PHP change tied to its original acceptance criteria. Use the [WordPress theme compatibility guide](/articles/showcase-idx-wordpress-theme-compatibility) for listing-theme questions instead of expanding this runtime brief into an IDX setup guide. Bring the approved requirements and acceptance checks to your [real estate website brief](/for/real-estate). Request the work through the [written website scope](/work). - [Website maintenance contract checks for real estate agents](/articles/agent-website-maintenance-agreement-checks) - [WordPress security updates: a care policy for real estate websites](/articles/agent-wordpress-security-update-care-policy) - [Shared hosting vs VPS for a real estate website](/articles/shared-hosting-vs-vps-agent-website) ## Related: Real estate - [Website maintenance contract checks for real estate agents](/articles/agent-website-maintenance-agreement-checks) - [WordPress security updates: a care policy for real estate websites](/articles/agent-wordpress-security-update-care-policy) - [Shared hosting vs VPS for a real estate website](/articles/shared-hosting-vs-vps-agent-website) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```