WordPress 7.1 Update Guide: Back Up First, Then Test
What WordPress 7.0 and 7.1 brought, why the 7.1.1, 7.1.2 and 7.1.3 security releases matter, and how a business site can prepare for the update.
rabbitclip teamPublished: 6 min read
Short answer
For a business running WordPress, the right order is this: take a full backup first, try the update on a test copy, then bring the live site up to the current security release, which as of today is 7.1.3. According to the WordPress.org announcements, 7.1.1, 7.1.2 and 7.1.3 all carry security fixes, so putting the update off, particularly after 7.1.2, may leave your site exposed to known vulnerabilities.
WordPress 7.0 came out in May 2026 and 7.1 in August 2026. Both changed the dashboard and the editor in visible ways, but for a business site the real question is less what the new features are and more whether your existing plugins and theme will run smoothly on these versions.
Below you will find what the two releases brought, what the security releases say, how to prepare for the update step by step, the mistakes made most often, and the situations in which not rushing is reasonable.
What did WordPress 7.0 Armstrong bring?
According to the WordPress.org announcement of 20 May 2026, the headline change in 7.0 is an AI Client added to Core. The announcement says it lets WordPress communicate with generative AI models, with connections managed from a single hub in the dashboard. Alongside it, an optional AI plugin offers image generation and editing, title and excerpt writing, and alt text suggestions.
Beyond that, the dashboard received a new colour scheme, images gained a revision history and the editor gained new blocks. Real-time collaborative editing is not in this release. We say so plainly to keep expectations accurate.
- An AI Client in Core and a single connection hub in the dashboard
- An optional AI plugin: image, title, excerpt and alt text suggestions
- New Gallery, Heading, Breadcrumbs and Icons blocks
- Responsive visibility controls and customisable menu overlays
- Server-side block and pattern registration in PHP
What did WordPress 7.1 Mary Lou change?
According to the WordPress.org announcement of 19 August 2026, 7.1 lets you set block styles by screen size without writing custom CSS, from Global Styles or from the block settings. You can also preview at different viewport widths while editing. A new media editor window brings cropping, flipping, rotating and metadata editing together.
The change that touches your server is that image compression, resizing and thumbnail generation now happen in the browser. The announcement says this reduces server load. Support for AVIF, HEIC and HDR gain maps arrived too. Real-time collaborative editing is missing from 7.1 as well.
- Block styles by screen size, no custom CSS needed
- New media editor window: crop, flip, rotate, metadata
- Rich text, @mentions and notes on text selections in Notes
- In-browser image compression and thumbnails; AVIF, HEIC and HDR gain map support
- Playlist and Tabs blocks, plus hover, focus and active styles on Button blocks
Why do the 7.1.1, 7.1.2 and 7.1.3 security releases matter?
According to the WordPress.org announcements, 7.1.1 came out on 17 September 2026 with 11 security fixes, 17 Core fixes and 19 block editor fixes. 7.1.2 followed on 22 September 2026 with a fix for a single critical severity vulnerability. 7.1.3, on 6 October 2026, carries 7 security fixes and 4 bug fixes. We do not describe the individual flaws here; the official announcements are the right place for that.
That rhythm shows something: security releases arrive in close succession, so treating updates as a once a year job does not work. Minor releases rarely bring new features, which also makes them easier to test. You can look at the basic security state your site shows to the outside with rabbitclip's security check.
How do you prepare for the update?
The order is simple and dull, and it protects you. First take a full backup covering files and database, and try restoring it once; a backup that cannot be restored is not a backup. Then open a copy of the live site in a test environment and apply the update there.
In the test copy, do not look at the home page alone. Walk through the paths that bring your business money or customers one by one: the contact form, the booking or order flow, the payment page, the login. We do not give the required PHP and MySQL versions here because our sources do not state them; confirm requirements from the WordPress.org announcement or from your hosting company.
- A full backup of files and database, with a restore test
- A test copy of the live site
- The developer's compatibility note for each plugin and theme
- Forms, payments, login and booking tried one by one
- Site speed measured after the update; rabbitclip's site speed tool can do that
What mistakes are common when updating?
The most common mistake is pressing the update button on the live site without a backup. The second is thinking of plugins apart from Core: updating WordPress and leaving an old plugin behind is where trouble usually appears. The third is keeping automatic updates off on a site nobody watches and not noticing for weeks.
There is also the temptation to switch the AI connection on out of enthusiasm for the new features. The connection is an optional setting; turning it on without knowing which account and which data it uses is your responsibility.
- Updating the live site without a backup
- Updating WordPress but leaving an old plugin behind
- Postponing updates endlessly on an unwatched site
- Switching on the AI connection without knowing where data goes
When is this update unnecessary or the wrong choice?
None of the new features is mandatory. If your site works today and you do not need what the editor now offers, you need not spend time trying every new block in 7.1. The security fixes stand outside that calculation, though: postponing them, especially after 7.1.2, is the wrong choice.
If your site depends on a very old plugin or a custom theme, the riskiest move is to jump a major version with no testing at all. In that case measure compatibility first and, if necessary, replace the plugin or rebuild the theme. Do not try to finish that in a single evening.
To sum up: take a backup, update a test copy, then bring the live site to 7.1.3 and from now on do not let security releases wait. The new features are pleasant if you need them and no reason to hurry if you do not. If you would like to read your site's current state and plugin compatibility together, we are glad to have a calm discovery conversation with you at rabbitclip.
FAQ
Is updating to WordPress 7.1.3 mandatory?
It is not mandatory, but it is recommended. According to the WordPress.org announcements, 7.1.1, 7.1.2 and 7.1.3 carry security fixes, and one of them closes a vulnerability of critical severity. Holding security releases back puts the site at needless risk.
What should I back up before updating?
Both the files and the database. Taking the backup and then trying a restore shows that it really works. If your hosting company keeps a backup, store a copy of your own as well.
Will my plugins work with 7.1, and how do I find out?
Look first at the compatibility note on the plugin developer's page, then update a test copy and try the critical flows one by one. If there is no compatibility information, or the plugin has not been updated for a long time, consider an alternative.
Do I have to switch on the AI plugin?
No. According to the WordPress.org announcement, the AI plugin is optional. Before enabling it, be clear about which account will be connected and which content will be sent.
Sources
The specific facts in this article rest on these official pages; check them for the current position.
