Web Hosting

PHP 8.6 WordPress Hosting: What to Ask Before WordPress 7.2

Server racks in a data center, for PHP 8.6 WordPress hosting

As of 2026-11-19 UTC. PHP 8.6.0 was released on November 19, 2026, according to the php.net release page. The WordPress Developer Blog covered what it means for WordPress in What’s new in PHP 8.6 and what that means for WordPress?, published November 18, 2026.

What PHP 8.6 changes for a WordPress site

PHP is the language WordPress is written in, and your host normally decides which version runs underneath your site (general hosting knowledge, not from the cited posts). That is why PHP 8.6 WordPress hosting is worth a few minutes of attention even if you never write code. The WordPress Developer Blog describes PHP 8.6 as bringing “1 INI directive, 15 enums, 17 functions, 24 classes, 47 constants, and 1 interface” as new additions, along with “Deprecations for 26 functions and 2 constants” and “Removals of 2 extensions, 15 functions, and 2 classes.”

The features the post highlights are aimed at developers: partial function application, a clamp() function that keeps a value between a minimum and a maximum, a Duration class for time intervals, more URI handling classes, and closure optimizations. The post says it does not expect to see these in WordPress core “any time soon,” as long as the minimum supported PHP version is not moved closer to recent releases. It adds that the closure optimizations need nothing from WordPress beyond being compatible with PHP 8.6.

How PHP 8.6 lines up with WordPress 7.2

For PHP 8.6 WordPress hosting, the timing matters. The Developer Blog post says PHP 8.6 arrives “just 2 days after” WordPress 7.2 RC1. The RC1 announcement, dated November 17, 2026, gives December 8, 2026 as the scheduled final release date and lists “Accessibility, security, and PHP 8.6 compatibility improvements” among the release highlights. A later release note, the WordPress 7.1.5 announcement, adds that “WordPress 7.2 RC 2 has also been released, containing all applicable fixes.”

The post explains what the compatibility work looks like. PHP 8.6 was added to the PHPUnit test matrix for the 7.2 development cycle. In a comment, Jonathan Desrosiers wrote that as of November 10 (r65384) the PHPUnit tests running on PHP 8.6 are no longer allowed to fail, and that “All known compatibility issues in WordPress itself have been resolved.” That is one commenter’s statement, not a formal compatibility notice. Core is also only one part of a site: themes, plugins and custom code run on top of it, and PHP 8.6 WordPress hosting depends on those too (general WordPress knowledge).

Which old PHP functions are being deprecated

The post says WordPress core and “extenders” should search their code for the deprecated functions. It says PHP 8.6 is deprecating Oniguruma-based mbstring regex functionality, including mb_ereg(), mb_ereg_replace() and mb_split(). It describes the 8.6 deprecations as proposed for removal in PHP 9. The php.net release page gives the reason for the mbstring change: the underlying Oniguruma library is no longer maintained.

The same php.net page lists the replacements. The is_double(), is_long() and is_integer() aliases are deprecated in favor of is_float() and is_int(), and spl_object_hash() is deprecated in favor of spl_object_id(). A plugin changelog that mentions PHP 8.6 compatibility may well be about swaps like these.

The post lists other deprecated functions that need auditing, with match counts across WordPress plugins: spl_object_hash() “found 8,772 matches across 2,359 WordPress plugins,” is_double() “found 790 matches across 311 WordPress plugins,” is_integer() “found 2,720 matches across 887 WordPress plugins,” and is_long() “found 10,809 matches across 2,258 WordPress plugins.” The post describes these as matches for the old function names. It does not say how many plugins would actually break. On compatibility, it says what to expect is mostly deprecation notices, and mostly in tests.

The PHP 8.6 WordPress hosting gap: version 7.4 is still the minimum

The post states that the minimum PHP version supported by core and plugins is, “since WordPress 7.0, PHP 7.4.” That is why core cannot yet design around features from PHP 8.0 onward, such as named arguments, enums and readonly properties. That matters for PHP 8.6 WordPress hosting because many sites sit well behind the newest version.

The post gives a sense of how wide: “In April this year, ~20.5% of WordPress websites were running on PHP 7.4, and now, at the end of October, we’re looking at ~17%.” That is real movement, but it is roughly one site in six still on the oldest supported version at the end of October. The post adds that once a version’s share drops below 5%, the minimum is bumped, provided the other criteria are met.

What to ask your host this week

Nothing in the sources says PHP 8.6 requires action today. The urgent update this week is a different one, covered in our WordPress 7.1.5 security release post. For PHP 8.6 WordPress hosting, though, it is a sensible week to ask your host or developer which PHP version your site runs. Moving to a newer version is generally a low-drama change on a managed WordPress host, since it mainly affects speed and compatibility rather than how the site looks. (This is general hosting knowledge, not from the cited posts.) Good questions for any PHP 8.6 WordPress hosting conversation:

  • Which PHP version does my site run now, and can I switch versions myself?
  • Do you offer PHP 8.6 yet, and is there a staging copy where I can test first?
  • Do any of my plugins or my theme mention PHP 8.6 compatibility in their changelogs?

If you run an unmanaged server, the tradeoffs between managed and unmanaged VPS hosting are worth revisiting, because on an unmanaged VPS the version upgrades and testing fall to you or your developer. WordPress 7.2 is scheduled to ship on December 8, so test your theme and plugin combination on a staging copy before then. Our earlier post on the WordPress 7.2 Secrets API covers another change in that release.

What the sources do not say

The Developer Blog post does not give a release date for PHP 9, so the sources give no date by which the deprecated functions would be removed. The post tells extenders to “follow the core example” when replacing the mbstring functions, but it does not say which deprecated calls core has changed or which remain. The “feature gating” idea, offering new features only to sites on a modern PHP version, was suggested by someone at a WordCamp US 2026 discussion, and the author says they like the idea; it is not a confirmed plan for core. Finally, the PHP 7.4 share figures cite a source the post links to, and this article has not checked how they were measured.

Featured image: “Awaiting servers” by bugeaters, licensed CC BY 2.0, via www.flickr.com.