Quick answer: WordPress 7.1 “Mary Lou” is the second major WordPress release of the year, released on 19 August. It is a polish-and-finish release: easier responsive design controls without custom CSS, faster image uploads, new blocks such as Tabs, and improvements to the editing and collaboration experience. Most Australian business sites can update safely if they take a full backup, test on a staging copy, check plugin and theme compatibility, and update during a quiet period rather than clicking the update button straight away.
If your website generates leads or sales, a major WordPress update is not something to leave to chance. The good news is that 7.1 is not a reinvention of the platform. The practical risk comes from the plugins, themes and custom code your site depends on, not from WordPress itself.
This guide explains what is new in WordPress 7.1, what it means for your business site, and a step-by-step process for updating without breaking anything. If you missed the previous release, start with our overview of WordPress 7.0.
What is new in WordPress 7.1?
WordPress 7.0, released in May, introduced native AI infrastructure and a redesigned admin dashboard. WordPress 7.1 builds on it by finishing styling and media features and polishing the experience. The main changes reported for 7.1 are:
- Responsive design controls in the editor. You can adjust how blocks look on different screen sizes without writing custom CSS. This is helpful for business owners who previously needed a developer for small mobile layout fixes.
- Interactive styling states. More control over how blocks look when someone hovers over or focuses on them, such as buttons and links, using the Site Editor instead of code.
- A new Tab block. Build tabbed content, such as service details or FAQs, without a plugin.
• Faster image uploads. Client-side media processing handles more of the image work in the browser, which can speed up uploading large photos. - Collaboration and editing improvements. Refinements to features such as Notes and the day-to-day editing experience.
- Admin polish and bug fixes. A long list of fixes across the dashboard, block editor and media library, plus some security hardening, although 7.1 is not primarily a security release.
What did not make it into 7.1
Some features people expected did not arrive:
- Real-time collaborative editing (several people editing the same page at once, like Google Docs) was pulled from 7.0 over stability concerns, and it was not included in 7.1 either.
- React 19 was deferred, so the editor stays on its current React version.
This list is based on reports from the WordPress community and hosting providers. Always confirm details against the official release notes on wordpress.org before relying on a specific feature.
Should your business update to WordPress 7.1?
Generally yes, because staying on older versions means missing security fixes and increasing the chance that new plugin versions stop supporting your setup. But how and when you update depends on how complex your site is.
| Type of site | Recommended approach |
|---|---|
| Simple brochure site with few plugins | Test on staging, then update within a week or two |
| Business site with forms, bookings or memberships | Test on staging, update in a planned maintenance window |
| WooCommerce or online store | Test on staging including a full checkout, and avoid peak trading periods |
| Heavily customised site or page-builder site | Have a developer review compatibility before updating |
| Site with custom plugins or theme code | Developer testing is essential before any update |
By default, WordPress installs minor and security updates automatically but does not install major releases like 7.1 unless you have turned that option on. Check Dashboard → Updates to see which setting your site uses.
Timing tip for Australian retailers: If you sell online, finish your updates before the lead-up to Black Friday and Christmas, and avoid major changes during peak trading. A broken checkout at that time costs far more than a delayed update.
Before you update: a pre-update checklist
- Take a full backup of files and database, and confirm you can restore it
- Store a copy of the backup somewhere other than your web server
- Check your PHP version meets the requirements for 7.1, and ask your host if unsure
- List every plugin and your theme, and check each plugin’s “Tested up to” version on its WordPress.org page
- Update plugins and your theme to their latest versions on the staging copy first
- Make a note of any custom code, custom CSS or snippets added to your site
- Identify your most important pages: home, contact, key service pages, checkout
- Choose a quiet time to update, such as late evening or early morning AEST
- Let your team know when the update is happening
How to update WordPress 7.1 safely, step by step
- Create a staging site. Most Australian hosts offer one-click staging. It is a private copy of your site where you can test the update without affecting visitors.
- Back up the live site. Do this even though you are testing on staging, in case you need to roll back.
- Update plugins and your theme on staging. Do this before updating WordPress core, so compatibility issues show up in a controlled order.
- Update WordPress to 7.1 on staging. Go to Dashboard → Updates and run the core update.
- Test the staging site thoroughly using the checklist below.
- Fix any problems on staging. Replace incompatible plugins, update custom code or ask your developer for help.
- Update the live site. Repeat the same order of updates on the live site during your maintenance window.
- Clear all caches. Clear your caching plugin, hosting cache and any CDN so visitors see the updated site.
- Retest the live site and monitor for errors over the next few days.
What to test after updating
- Home page and key service pages load correctly on desktop and mobile
- Menus, links and search work
- Contact, quote and booking forms submit, and notification emails arrive
- Login, registration and account pages work
- If you use WooCommerce: add to cart, checkout, payment, shipping rates and order emails
- Images upload and display correctly in the media library
- Page builder pages, such as Elementor layouts, still look right
- Custom CSS and custom code still behave as expected, especially now that responsive controls are built in
- Page speed has not dropped (check Core Web Vitals)
- Analytics, tracking codes and cookie notices still work
- Accessibility basics are intact. See our guide to website accessibility compliance in Australia
Common problems after a WordPress update and how to fix them
| Problem | Likely cause | What to try |
|---|---|---|
| “Critical error” message or white screen | A plugin or theme not compatible with the new version | Check the recovery-mode email, rename the plugins folder to disable all plugins, then reactivate them one at a time |
| Layout looks different | Theme or page builder conflict, or custom CSS clashing with new styling features | Update the theme or builder, clear caches, review custom CSS |
| Forms stop sending emails | Mail settings or an outdated form plugin | Update the form plugin and test your SMTP or mail settings |
| Editor won’t load or buttons don’t work | A plugin conflict or a cache issue | Clear caches, test in a private window, disable plugins one at a time |
| Site is slower | Cache needs rebuilding, or a plugin is not optimised | Clear and rebuild caches, then test for slow plugins |
| Something broke and you cannot fix it quickly | Multiple causes | Restore the backup you took before updating, then investigate on staging |
If the site goes down and you cannot get back in, our guide to what to do when a WordPress site breaks or is hacked covers the recovery steps.
How long does the update take?
These are typical ranges. Real timing depends on your plugins, your theme and how much testing your site needs.
| Site type/th> | Typical time |
|---|---|
| Simple brochure site | 1 to 2 hours including testing |
| Business site with forms and several plugins | Half a day |
| WooCommerce or membership site | 1 to 2 days with full testing |
| Heavily customised or large site | Several days, including developer review |
Why wait a little before updating?
New major releases are usually followed by point releases (for example 7.1.1) that fix problems found in the first few weeks. For most business sites, a short wait lets plugin developers release compatibility updates and lets early issues surface. The risks of waiting too long are missed security fixes and plugins that eventually stop supporting your WordPress version, so do not delay indefinitely. Check which 7.1 point release is current before you update.
Why regular WordPress maintenance matters
Every major release brings a round of plugin and theme updates. Without someone looking after them, small issues add up, from security gaps to slow pages and conflicts that eventually break your site. A maintenance plan gives you scheduled updates, backups, monitoring and a person to call when something goes wrong. Read our WordPress maintenance services guide for Australian businesses to see what a good plan includes.
Making the most of the new features
Once your site is stable on 7.1, there is real value to be had:
- Use the new responsive controls to fix mobile layout issues without custom CSS
- Replace tab or accordion plugins with the native Tab block where it fits
- Review your image workflow, since faster uploads help teams who publish often
- Combine the editor improvements with the AI features introduced in 7.0, and see our guide to optimising your WordPress site for AI search
Frequently asked questions
When was WordPress 7.1 released?
WordPress 7.1 was released on 19 August, on the final day of WordCamp US.
What is new in WordPress 7.1?
The main changes are responsive design controls, interactive styling states, a new Tab block, faster image uploads through client-side media processing, and editor and collaboration polish.
Does WordPress 7.1 include real-time collaboration?
No. Simultaneous real-time editing was pulled from 7.0 and was not included in 7.1.
Is it safe to update to WordPress 7.1?
It is safe for most sites when you back up first, test on a staging copy and confirm your plugins and theme are compatible. Complex or customised sites should have a developer review the update.
Will my plugins work with WordPress 7.1?
Most well-maintained plugins will. Check each plugin’s “Tested up to” version, update everything on staging first, and replace any plugin that is no longer maintained.
Do I have to update to 7.1 right away?
No, but do not leave it for too long. A short wait for the first point release is reasonable, while delaying for months increases your security and compatibility risks.
What if my website breaks after updating?
Restore your pre-update backup, then work out the cause on a staging copy. A common fix is disabling plugins one at a time to find the incompatible one.
Do I need a developer to update WordPress?
Simple sites can often be updated by the owner with a good backup. Online stores, membership sites and heavily customised sites are better handled by a professional.
Need help updating WordPress?
WP Professionals provides safe WordPress updates, staging, testing and ongoing maintenance for Australian businesses from our Melbourne and Sydney offices. Explore our WordPress services, or contact us or call 1300 72 50 90 for a free site health check and update plan. If you are still choosing a partner, read how to hire the right WordPress team and our 10 questions to ask a WordPress development company.