WordPress 7.0 and 7.1: What’s New and How to Update Safely (2026)

WordPress 7.0 “Armstrong” came out on 20 May 2026, and WordPress 7.1 “Mary Lou” followed on 19 August 2026. The latest release is 7.1.3, a security update from 6 October 2026. If your site still runs 7.0 or older, you should update, but do it in the right order: check PHP, back up, update plugins and themes, then update WordPress. This guide explains what changed and how to update without breaking your site.

Facts below come from the sources listed at the end, checked on 28 October 2026. Release details can change, so confirm on WordPress.org before you act.

WordPress versions at a glance

VersionRelease dateWhy it matters
7.0 “Armstrong”20 May 2026AI Client, Command Palette, redesigned dashboard, PHP 7.4 minimum
7.1 “Mary Lou”19 August 2026Responsive block styles, Tabs and Playlist blocks, new media editor, browser-side image processing
7.1.222 September 2026Security release
7.1.36 October 2026Security release with seven fixes (reported by Frontman)

What is new in WordPress 7.0

  • AI Client and Connectors: a built-in, provider-neutral way for plugins to talk to AI services. WordPress 7.0 ships no active AI features by default. You need a plugin and a connected provider.
  • Command Palette: press Ctrl + K (Cmd + K on Mac) to jump to any admin screen or action.
  • Redesigned dashboard: new colors and smoother transitions.
  • Editor tools: block-level custom CSS, per-device visibility controls, a font manager, and new blocks such as Breadcrumbs and Icons.
  • Higher requirements: PHP 7.4 is now the minimum. PHP 7.2 and 7.3 are no longer supported. WordPress recommends PHP 8.3 or newer.
  • What was dropped: real-time collaboration was removed shortly before release and is still not in 7.1.

What is new in WordPress 7.1

  • Responsive styles: edit block styles separately for desktop, tablet and mobile, and style hover and focus states for buttons.
  • New blocks: Tabs and Playlist (for audio tracks).
  • Media editor: a new modal editor with freeform or fixed-ratio cropping.
  • Notes: block comments now support rich text and @mentions.
  • Image processing in the browser: resizing and compression move from the server to the browser, with support for formats such as AVIF and HEIC. SmartWP calls this the change with the widest reach.
  • Always-on iframe editor: the post editor now loads in an iframe. This can affect plugins or custom code that rely on old editor behavior.
  • For developers: about 20 new hooks, and expanded Abilities API filters.

Should you update?

Yes. Only the newest WordPress version gets full security fixes, and 7.1.3 fixes seven security issues. A site on 7.0 or older should move to 7.1.3. If your site is business-critical, test the update on a staging copy first, because the iframe editor change is the most likely cause of problems with older plugins.

How to update WordPress safely

  1. Check your PHP version. Go to Tools > Site Health > Info > Server. You need PHP 7.4 at minimum. PHP 8.3 or newer is recommended. If you are below that, ask your host to upgrade PHP first.
  2. Make a full backup of your files and database. Store a copy outside your server.
  3. Update plugins and themes first. Go to Dashboard > Updates and update everything that has a compatible update. Remove plugins you no longer use.
  4. Test on staging if you can. Many hosts offer a one-click staging copy.
  5. Update WordPress. On Dashboard > Updates, select Update to version 7.1.3 (or the newest listed). Do not close the tab until it finishes.
  6. Test your site. Open the home page, a post, the contact form, search, login, and (if you sell things) checkout. Create a draft post and check that the editor, image upload and Publish button work.

Troubleshooting WordPress update problems

The site is stuck in maintenance mode

This happens when an update is interrupted. Use FTP or your host’s file manager to delete the .maintenance file in your WordPress root folder (the same folder as wp-config.php). It may be hidden, so turn on “show hidden files”. Then reload the site and run the update again.

White screen or critical error after updating

  1. Check your email. WordPress often sends a recovery link to the admin address.
  2. If that fails, rename the wp-content/plugins folder to plugins-off using FTP. If the site loads, a plugin is the cause. Rename it back and rename plugins one by one to find it.
  3. Switch to a default theme the same way by renaming your active theme’s folder.
  4. Turn on debugging by setting WP_DEBUG and WP_DEBUG_LOG to true in wp-config.php, then read wp-content/debug.log. Turn debugging off afterwards.
  5. If you cannot fix it quickly, restore your backup and try again on staging.

The update fails or says it could not copy files

Common causes are low disk space, wrong file permissions, or a short time limit on the server. Ask your host to check free space and permissions. You can also update manually: download WordPress from WordPress.org, upload the new wp-admin and wp-includes folders, and copy the new files in the root folder. Do not overwrite wp-content or wp-config.php.

The editor looks broken or a custom block stopped working

WordPress 7.1 always loads the post editor in an iframe. Plugins with older editor code may break. Update the plugin, check its support page for 7.1 notes, or temporarily deactivate it. If it is a custom block you wrote, test it on staging and read the 7.1 developer notes.

“Your PHP version is too old” or the update does not appear

WordPress does not offer an update if your PHP is below the minimum. Ask your host to switch PHP to 8.3 or newer in the hosting panel, then check for updates again.

Images look different or uploads fail

7.1 moves image processing into the browser. If an upload fails, try another browser, disable image-optimization plugins to test, and check that your browser is up to date. I did not find a single official fix list for this, so treat it as a checklist to try, not a confirmed cure.

Common mistakes

  • Updating WordPress before checking PHP. This is the most common cause of a blocked update.
  • Skipping the backup. A backup on the same server can be lost with the site.
  • Updating on a live shop during busy hours. Pick a quiet time.
  • Ignoring plugin updates. Old plugins cause most post-update errors.
  • Turning on AI features without reading the settings. Core makes no AI calls until a provider is connected, so you stay in control.
  • Staying on 7.0 because it works. Security fixes now go to 7.1.x.

Practical examples

  • Small blog on shared hosting: back up, update plugins, update to 7.1.3, then test one post and your contact form.
  • Online store: clone to staging, update there, place a test order, then update the live site at night.
  • Site on PHP 7.4: it works with WordPress 7.1, but ask your host about PHP 8.3 or newer. Test on staging first.
  • Site with a custom block plugin: test the block in the new iframe editor on staging before updating live.

Hosting too limited for staging or backups? See our guide to shared vs VPS hosting. If your site shows an error after updating, our fix for the database connection error may help.

FAQ

What is the latest WordPress version?

As of 28 October 2026, the latest release I found is 7.1.3 (6 October 2026). Check WordPress.org for anything newer.

Does WordPress 7.0 or 7.1 add AI features to my site?

Not by default. Core adds the AI Client and a Connectors screen, but it makes no AI calls until a plugin or theme uses a connected provider.

What PHP version do I need?

PHP 7.4 is the minimum for 7.0 and later. WordPress recommends PHP 8.3 or newer.

Can I go back to an older version?

Restoring a backup is the safe way. Manual downgrades can break the database, so avoid them.

Is real-time collaboration available?

No. It was removed before 7.0 and is not in 7.1. Notes, which are asynchronous block comments, are available.

Sources

Share this post:

Leave a Comment

Your email address will not be published. Required fields are marked *

WhatsAppFacebookXLinkedInTelegram
Scroll to Top