WordPress 7.2 Is Coming: 6 Steps to Prep Your Site

Web Design

Table of Contents

Laptop screen showing website code while preparing a WordPress 7.2 update

WordPress 7.2, the last major WordPress release of the year, is scheduled to ship on December 8, and the fifth beta landed on November 10 with a warning that every site owner should read: WordPress core is ready for PHP 8.6, but your plugins and theme may not be. If your business website runs on WordPress, the next four weeks are your window to back up, test on a copy of your site, and confirm your plugins are compatible before the update reaches your live site. A little preparation now prevents a broken contact form or a blank homepage in the middle of the holiday rush.

Key Takeaways

  • WordPress 7.2 is scheduled for final release on December 8, with Release Candidate 1 due November 17 and two more release candidates on November 24 and December 1.
  • Beta 5, released November 10, resolved all known core compatibility issues with PHP 8.6, which is scheduled for release on November 19.
  • The WordPress team says you must verify that every plugin and theme you use is compatible with PHP 8.6 before upgrading your server.
  • The release ships a new default theme called Ipsum, a Secrets API for storing API keys securely, and in browser image compression for the Media Library.
  • Beta 5 also adds an email notification whenever someone creates an application password on your site, which helps you spot unauthorized access.
  • Business owners should back up, test on a staging copy, and update plugins first, then update WordPress core after the first maintenance release if the site is mission critical.

What Is Changing in WordPress 7.2 and When Does It Arrive?

WordPress publishes its release calendar in public, so the dates are not a guess. According to the official WordPress 7.2 release schedule, Beta 1 arrived on October 20, Beta 5 arrived on November 10, Release Candidate 1 is planned for November 17, and the final version is planned for December 8. A release candidate (RC) is a version the team believes is ready to ship unless testers find a serious bug, so RC 1 is the point where agencies and developers start testing in earnest.

The WordPress 7.2 Beta 1 announcement lists the headline features. Most of them live inside the block editor and the WordPress dashboard rather than on the public face of your website:

  • Ipsum, a new default theme. Brand new sites will start with Ipsum. Existing sites keep whatever theme they use today.
  • More responsive design controls. Designers get more settings that change by screen size, including gallery columns, cropping, and aspect ratios on phones versus desktops.
  • Text shadow controls and better Global Styles tools for keeping fonts and colors consistent site wide.
  • Faster media uploads. Images can now be resized, compressed, and converted in the browser before they reach your server, which helps on budget hosting plans.
  • A faster dashboard. Admin scripts and stylesheets now load individually for better caching, and WordPress prefetches the admin screen you are likely to open next.
  • A Secrets API. A standard, encrypted place for plugins to store API keys and tokens, such as the keys that connect your site to your CRM, payment processor, or email platform.

For a business owner, the practical meaning is simple: this is a refinement release, not a redesign of your website. Your visitors will not see a new look on December 8. The risk is not the new features. The risk is the moving parts around them.

Why Should a Business Owner Care About PHP 8.6?

PHP is the programming language WordPress and nearly every plugin are written in. Your web host runs a specific PHP version on the server, and that version has to be compatible with WordPress core, your theme, and every plugin at the same time. The WordPress 7.2 Beta 5 release post says PHP 8.6 is scheduled for release on November 19 and that, as of Beta 5, all known PHP 8.6 compatibility issues in WordPress itself have been resolved.

The important sentence for owners comes next. The WordPress team says you will need to verify that all of your plugins and themes are also compatible with PHP 8.6 prior to upgrading. In plain terms, WordPress has done its homework, but the plugin that powers your booking calendar, your quote form, or your store checkout may not have.

Here is how that usually goes wrong. A host offers a one click PHP upgrade, or moves accounts to a newer version automatically. One older plugin calls a function that the new PHP version removed or changed. The result can be a white screen, a “critical error” message, or a form that looks fine but silently stops sending leads. We have seen the silent form failure more than once, and it is the most expensive version because nobody notices for days.

So treat these as two separate decisions. Updating WordPress core is one change. Upgrading your server to PHP 8.6 is another. Do not make both changes on the same afternoon, and do not make either one on your live site without testing first.

How Does WordPress 7.2 Compare to What Your Site Runs Today?

The table below separates what changes automatically, what you control, and what you should do about each item before December 8.

ChangeWho It AffectsRisk to Your BusinessYour Move
Core update to WordPress 7.2Every WordPress site, on the schedule your host or settings allowLow for core itself, higher if plugins are outdatedBack up, update plugins first, test on staging
PHP 8.6 on your serverSites whose host upgrades PHP or offers it as an optionMedium to high if any plugin or theme is not readyWait until every plugin confirms support, then switch on staging first
Ipsum default themeNew sites, and sites still using an old default themeLow, existing custom themes are not replacedNo action unless you run a default theme
In browser image compressionAnyone uploading photos to the Media LibraryPositive, smaller files can help page speedKeep uploading properly sized images, recheck image quality after updating
Secrets APIPlugins that store API keys for CRMs, payments, and email toolsPositive once plugins adopt itAsk your developer which integrations will use it
Application password alertsAny site where users can create application passwordsPositive, flags possible unauthorized accessMake sure admin emails reach a monitored inbox

Notice that most rows are either low risk or positive. The single row that deserves real attention is PHP. That is where preparation earns its keep.

Blue lit web hosting server rack where website backups and PHP updates run

What Should You Do Before WordPress 7.2 Ships?

Work through these steps in order. For a typical small business site with 15 to 30 plugins, this takes one to three hours, and most of that time is waiting for backups and tests to finish.

6 Steps to Get Your Site Ready for the Update

1

Take a full backup you can actually restore

Back up files and the database, store a copy off the server, and confirm you know how to restore it. A backup you have never tested is a hope, not a plan.

2

Make a staging copy of your website

Most managed hosts offer one click staging. Every update in this list happens there first, never on the live site.

3

Inventory every plugin and theme

List each one with its version and last update date. Flag anything not updated in 12 months or marked as closed in the WordPress plugin directory.

4

Update plugins and theme before core

Update everything on staging first, including Elementor and Elementor Pro if you use them, then test your forms, checkout, booking tools, and menus.

5

Test the release candidate on staging

Once Release Candidate 1 is out on November 17, your developer can run it on staging and click through your top 10 pages and every lead form.

6

Schedule the live update and the PHP switch separately

Update core first. Move to PHP 8.6 only after every plugin vendor confirms support, and send a test lead after each change.

If you run a mission critical site, such as an online store or a site that books appointments around the clock, it is reasonable to wait for the first maintenance release (usually 7.2.1) before updating your live site. The exception is security releases. When WordPress ships a security fix, such as WordPress 7.1.4 on October 28, apply it promptly. Our post on why WordPress security releases should be applied quickly explains how to tell the two kinds of updates apart.

Will WordPress 7.2 Break My Elementor Site?

There is no known reason WordPress 7.2 should break a well maintained Elementor site, but outdated plugins are the most common cause of update problems on any WordPress site. Elementor builds pages with its own editor, so many block editor changes in this release, like text shadows and new Global Styles filters, will not change how your Elementor pages look. What can still matter is the shared foundation: the PHP version, the admin dashboard, and the dozens of add on plugins many Elementor sites rely on.

Here is exactly what to check on staging after updating:

  • Open three of your most important pages in the Elementor editor and confirm they load and save.
  • Submit every contact, quote, and booking form and confirm the email or CRM entry arrives.
  • Check your header, footer, and mobile menu on a phone sized screen.
  • Run a page speed test on your homepage before and after so you can compare like for like.
  • Look for “critical error” emails from WordPress, which are sent to the site admin address.

If any of these fail, roll back on staging, identify the plugin responsible, and wait for its update before touching the live site. That is the whole point of a staging copy.

Common Mistakes to Avoid With WordPress 7.2

  • Updating directly on the live site. It works most of the time, which is why it feels safe until the one time it costs you a weekend of leads.
  • Upgrading PHP and WordPress on the same day. If something breaks, you will not know which change caused it.
  • Ignoring abandoned plugins. A plugin with no update in over a year is the most likely to fail under PHP 8.6 and the most likely to carry an unpatched security hole.
  • Relying on a backup you have never restored. Test the restore once on staging so you know it works.
  • Sending admin emails to an inbox nobody reads. The new application password alerts and critical error emails only help if someone sees them.
  • Testing the homepage only. Forms, checkout, and booking pages are where breakage costs money, so test those first.

How FOG Helps San Antonio Businesses Update Safely

At FOG Digital Marketing in San Antonio, we treat every major WordPress release as a scheduled project, not a button to press. Our website maintenance services include off site backups, staging tests, plugin audits, and post update form checks, so you hear about a problem from us instead of from a customer. If your site is older and the audit shows too many abandoned plugins, our San Antonio web design team can rebuild it on a lean, modern stack. And if speed is the concern, a technical SEO review measures Core Web Vitals before and after each update so you can see the effect. Pages that need to convert, such as ad landing pages, get the same treatment through our landing page design work.

Hosting matters here too. The recent DreamHost breach was a reminder that your host is part of your security plan, and your URL setup matters for search after any rebuild, as covered in our guide to Google’s updated URL guidance.

Frequently Asked Questions About WordPress 7.2

  1. When will WordPress 7.2 be released?
    WordPress 7.2 is scheduled for release on December 8. Release Candidate 1 is planned for November 17, with RC 2 on November 24 and RC 3 on December 1, according to the official release schedule.

  2. Will WordPress 7.2 update my site automatically?
    It depends on your settings and your host. By default, WordPress applies minor and security releases automatically, while major releases like 7.2 may need to be started manually unless you or your host have enabled automatic major updates. Check Dashboard, then Updates, to see your current setting.

  3. Do I need PHP 8.6 to run WordPress 7.2?
    No, the new version adds support for PHP 8.6 but does not require it. You can update WordPress and keep your current supported PHP version until every plugin and theme you use confirms PHP 8.6 compatibility.

  4. Will the new Ipsum theme change how my website looks?
    No, Ipsum only becomes the starting theme for new installs. Your existing theme, including an Elementor based design, stays in place after the update.

  5. Should I wait before updating?
    Waiting a short time is reasonable for business critical sites. Test on staging first, update plugins, and consider updating the live site after the first maintenance release, but always apply security releases promptly.

WordPress 7.2 is a solid, careful release, and the WordPress team has done its part on PHP 8.6. Your part is a backup, a staging test, and an honest look at your plugin list. Do those three things in the next few weeks and December 8 will be just another day for your website, which is exactly what you want.

Is Your Website Ready for the Next WordPress Update?

FOG Digital Marketing backs up, stages, and tests your WordPress site before every major release, so your forms, checkout, and booking tools keep working. Book a free 30 minute call and we will review your plugins and PHP readiness with you.

Our Blog

Website Design Blogs