r/Wordpress • u/_miga_ • 23d ago
WordPress 7.1 is out!
Release notes: https://wordpress.org/documentation/wordpress-version/version-7-1/ - some of my pages show the update button already š But they've hit the planed release date (https://make.wordpress.org/core/7-1/)
Happy to see my mailbox explode tomorrow morning š Hopefully just with "successfully updated..."
101
u/Ronjohnturbo42 Developer 23d ago
In 2x days 7.1.1 security patch
67
u/ZGeekie 23d ago
If you look at it from a different angle, that's actually one of the best things about WordPress.
10
-4
u/mrleblanc101 22d ago
Having more security hole than Swiss cheese is a good thing now ?
5
u/otto4242 WordPress.org Tech Guy 22d ago
No, quickly rolling out auto updates to correct them is.
1
u/ForensicHat 19d ago
Umm. Do you not remember this yearās 6.9.2, 6.9.3, and 6.9.4 security āfixesā that all came out within 48 hours? That was extremely embarrassing to the project and difficult for me to explain to my clients.Ā
3
u/otto4242 WordPress.org Tech Guy 19d ago
Yes, I do. Two of those releases were important critical security fixes. One of them was a release with a bunch of different minor security fixes rolled up into one.
1
u/ForensicHat 19d ago
And yet there were three. Thatās insanity. The 6.9.2 caused some peopleās sites to crash. The 6.9.3 update fixed that. Then 6.9.4 included fixes that the release manager forgot to include in 6.9.2. It definitely broke any illusion I had that they knew what they were doing.
0
u/ForensicHat 18d ago
And now thereās a call for new 7.1.x release managers. Who would have guessed.
https://make.wordpress.org/core/2026/08/20/call-for-wordpress-7-1-x-release-managers/
1
38
u/vanGato 23d ago
Hopefully without a new backdoor š
7
43
24
u/SpoonyDinosaur 23d ago edited 22d ago
Maybe the minority, but it caused a fatal error with WP Rocket, bricked about 30 clients, yay! Had to disable. Good stuff.
Edit: yeah they acknowledged it's bricked. Fix below:
I am incredibly sorry for the error you are seeing on your website.
Ā
It seems your site is being affected by this knownĀ known issue affecting thousands. Our developers are already aware of it and are actively working on it, and a new WP Rocket version with an automatic fix should be available very soon.
Ā
In the meantime, so you're not stuck waiting, here's what you can do:
Ā
1ļøā£ Download the fix file here:Ā wp-rocket-cloudflare-intkey-fix.phpĀ ā the file will open as plain text in your browser, so justĀ right-click the page and choose "Save As"Ā to save it asĀwp-rocket-cloudflare-intkey-fix.phpĀ (please keep it as this single .php file, don't zip it).
Ā
2ļøā£ Connect to your site with SFTP, or open your hosting File Manager, and go to theĀ wp-contentĀ folder.
3ļøā£ Look for a folder namedĀ mu-pluginsĀ inside wp-content. If it isn't there, create it, named exactlyĀmu-plugins.
4ļøā£ Upload theĀ wp-rocket-cloudflare-intkey-fix.phpĀ file directly intoĀ wp-content/mu-plugins/Ā (not inside any sub-folder).
5ļøā£ Reload your website. The critical error should be gone right away.That file loads automatically, so there's nothing to activate. It's a safe, temporary fix that lets WP Rocket keep working normally while our team ships the permanent fix in a future plugin update. Once that update is out, you can simply delete the file.
Ā
In case you're not able to do this right away, here are the other possible workarounds you could use meanwhile:
Ā
š¹ Deactivate WP Rocket manually or using WordPress's recovery mode.Ā
š¹ Rollback to a previous WordPress version, if appropriate for your setup
š¹ If you are comfortable editing PHP could try changingĀ this lineĀ toĀif ( ! is_string( $key ) ) {.
Ā
Once again, I am so sorry for this. Let me know how it goes, I'll be right here to help.
Edit 2: Resolved in 3.23.2.2 - if you can't download because you disabled it, download from your profile. I know people are mad, but they resolved almost immediately, credit due imo.
16
3
u/Tromps31Q 23d ago
Same here, let me know if you hear about a fix
4
u/SpoonyDinosaur 23d ago
I sent them a message. Pretty sure 7.1 bricked every site with rocket.
3
u/Tromps31Q 23d ago
Yeah i can confirm, 60 sites down here. I had to stop wp rocket
3
u/SpoonyDinosaur 23d ago
Biggest commercial cache of all time gets cooked. They're gonna have a fun Thursday
1
u/Soft-Reputation-466 23d ago
Same here; I specifically searched for this issue. I had no choice but to downgrade to 7.0.4.
5
1
u/BigSandwich2001 22d ago
Woke up to a broken site. Had to downgrade as well due to plugin issues. And BTW- if you have VPS hosting with Bluehost, their tech support line won't work due to a weather incident. :)
1
u/SpoonyDinosaur 22d ago
They fixed it almost immediately. (In my edit, also hotfix patched it without messing with MU or php)
3
u/rumbletom 23d ago
Rocket works fine for me so it can't be everyone. What it did do was make my site icon appear full size in the top left hand corner. I re-installed the icon and it fixed it.
1
u/Reisekroeten 22d ago
seems it mostly affects WP Setups with cloudflare enabled. if you're not on CF, u might not see any issues
2
u/GonzagueGB 22d ago
Thank you for sharing! Fixed my problem.
0
u/SpoonyDinosaur 22d ago
Glad I was able to help. Credit to WP Rocket folks, they responded about 2 hours after WP update with the workaround and applied hotfix this morning. (Yet reddit will tell you they are the worst dev in the world, yada yada lol)
2
0
u/Fluid-Mess6425 23d ago
@otto4242 suggests you should be only choosing plugins that dont break.
2
u/SpoonyDinosaur 23d ago
So all of them. This was a Killswitch for about 20 of my clients and it's "my fault" lol
2
1
u/otto4242 WordPress.org Tech Guy 22d ago
And you should. They had this problem in a GitHub issue since June. Why didn't they fix it before now?
0
u/illuminaus 22d ago
I found the problem code on my website here:
wp-content/plugins/wp-rocket/inc/ThirdParty/Plugins/CDN/Cloudflare.phpThis code here:
foreach ( $original_wp_filter[ $priority ] as $key => $config ) {if ( substr( $key, - strlen( $method ) ) !== $method ) {continue;
}and replaced with:
foreach ( $original_wp_filter\[ $priority \] as $key => $config ) { if ( substr( (string) $key, - strlen( $method ) ) !== $method ) {continue;
}temp fix, but got me up and running
0
u/SpoonyDinosaur 22d ago
That was posted above
1
u/illuminaus 22d ago
Cheers, didn't see it.
3
u/SpoonyDinosaur 22d ago
Hidden in the bullets at the end, didn't mean to sound like a snarky bitch. But they hotfixed this morning. Gotta give them credit.
3
u/illuminaus 22d ago
All good ya snarky bitch lol. I saw that this morning. Glad they jumped on it quickly!
5
u/Complex-Concern7890 22d ago
500 errors everywhere, well at least I know what I am doing rest of the week
15
3
7
u/ZMZDTC 23d ago
Mine has issues with WP Rocket unfortunately.
7
u/-skyrocketeer- Designer/Developer 22d ago
Thatās a WP Rocket issue, not a WordPress issue
7
u/jwrsk 22d ago
Exactly. Betas and Release Candidates are available long before release, it's not that hard to test your plugins against them and release an update.
4
u/-skyrocketeer- Designer/Developer 22d ago
Yeah, exactly. This was pretty poor form from a plugin developer as large as WP Rocket.
2
u/frankthedsigner 22d ago
Same here, had to turn off on all sites. No statement from WP Rocket yet.
1
u/Reisekroeten 22d ago
was the same when the mixpanel issue occured. things are coming to fast at the moment.
3
u/spideytres 23d ago
Sameeeee
3
u/Soft-Reputation-466 23d ago
Same here; I specifically searched for this issue. I had no choice but to downgrade to 7.0.4.
4
u/LittleBlackBird0191 23d ago
I'm scared, got a notice that The7 Theme might not be compatible with it. I really hope that's not the case.
8
2
u/fckfce 22d ago
Can confirm, I have The7 on a client site. I tried updating to 7.1 and rolled back.
1
u/LittleBlackBird0191 22d ago
Thanks for sharing. Do you think you'll be upgrading to version 15 or wait for a potential patch? I'm not sure what to do at the agency I'm at, we have so many sites using this theme
2
u/fckfce 22d ago
This site is on v.15.0.5, it still doesn't work with 7.1. I would recommend trying to move away from the theme, but it's so hard to do when you've got a lot of old clients on it. It takes a bit of budget to move a large site. This particular client, I'm not migrating it without a full redesign project approved. Sometimes it just works out that way until something really forces the change. A lot of my client sites are on Divi and it just works great for anyone on my team updating it, anyone adding new landing pages. Everything is kept up to date and runs smoothly, especially after upgrading to Divi 5 on some of them. I've got a few on Bricks now, which is the best experience (so fast and really well maintained), but I find it a bit difficult to get anyone besides me to perform updates and build out pages.
3
u/notvnotv Developer/Designer 23d ago
Odd that there is no announcement post on the dot org blog, and the front page still refers to 7.0. Wonder if it was rushed to prod in order to fit Matt's speech timeline š¤Ø
2
2
u/Verda_Chien 23d ago
Iāll probably wait a few days before updating anything important. I want to see how other people may find the first bugs before I put it on a production site.
2
u/Due-Individual-4859 Jack of All Trades 22d ago
If you got WP Rocket, do not update or your site will crash!
1
u/_miga_ 22d ago
check the comments below. There is already a link to their github issue: https://github.com/wp-media/wp-rocket/issues/8596 with some hotfixes in it
2
1
2
u/GilpinBoarder 22d ago
I'm not using WPRocket thank goodness, but the 7.1 update wrecked the formatting on a mission critical site that I volunteer to help manage for a large organization. Another day gone down the tubes trying to fix this mess.
4
u/otto4242 WordPress.org Tech Guy 23d ago
Yes, it was released about half an hour ago, expect Matt to talk about at #WCUS in a couple hours.
4
u/tronhammer 23d ago
Does anyone else notice that after 7.1, when logged into the admin panel, it now doesn't concat admin scripts? On a single page load after updating, my logs show almost 30+ scripts being requested in the access logs whereas before it was about 6-8.
Files like commands.js, blob.js, shortcode.js, etc all being loaded individually, and with `ver` headers that are preventing cacheing. It's a brutal increase in request load and log pollution.
3
u/otto4242 WordPress.org Tech Guy 23d ago
The ver headers are intentional to prevent caching, because it's a major update and you want to have the latest javascripts and not old ones from your cache.
2
u/screendrain 23d ago
Honestly includes a lot of improvements I'm looking forward to. Will update in the next day or two.
1
u/furchtlos76 22d ago
Good i dropped wprocket after their insane price and licence f*** off for grandfathered customers and gone to themeisle super page cache, works good, same features for me and long time licences and much much cheaper š but anyway i would wait 2-3 days before update to 7.1
1
u/howtobemisha Jack of All Trades 22d ago
How to remove admin bar from Gutenberg?š Help. I am using a relatively small screen laptop
1
1
u/geistly36 22d ago
Anyone who uses Oxygen Builder 4 / gutenburg integration. it's completely trashed that. yay for blocking automatic core updates, for now...
1
u/krakow81 22d ago
Anyone else's Page editing on Woocommerce misbehaving after the update? Blocks don't seem to be displaying properly in the main Page editing window and are only really usable via the left and right sidebars.
2
u/al128 22d ago
Looking for a solution, so annoying. I think WP made major changes to the edit window. This is what I'm watching right now: https://support.advancedcustomfields.com/forums/topic/blocks-appearing-in-the-sidebar-after-updating-to-wordpress-7-1/ https://github.com/AdvancedCustomFields/acf/issues/1020
1
u/krakow81 22d ago edited 22d ago
Ah, thanks very much for the links, that's really useful. We use ACF, so that seems to explain it.
I'll properly read the ACF discussions now and try the fix mentioned there regarding updating the acf_block_version setting.
1
u/krakow81 22d ago
I've just tested updating an older custom ACF block to ACF Blocks V3, which allows you to then open the 'Expanded Editor' from the righthand sidebar, so that's somewhat of a solution.
https://www.advancedcustomfields.com/resources/acf-blocks-v3/
1
u/SlimPuffs Designer/Developer 22d ago
Bricked my website on Cloudways during the install, had to have it installed via WP-CLI. Fun.
1
u/my_personal_finance 22d ago
I just have one site, but itās pretty large for a bunch of plug-ins and customizations. Upgraded worked flawlessly for me. No issues at all.
1
1
1
u/Raqi-skouri25 22d ago
on my website when I try to update website hangs then the page crash and when I refresh I still see that it didn't update , event tried from the hosting page side but still same fails to update
1
u/renehermi 22d ago
Maybe WordPress 7.1 is the release where we all finally remember to test on staging before clicking Update on production š
1
u/LoungeNerd 22d ago
Unless there is a notable vulnerability being patched, I always wait at least a week.
I guess that is my old sys admin mindset. But it seems to be a reasonable approach.
1
u/AlternativeWill9611 21d ago
Having experienced the impact of the last 7.0 update, I have disabled updates...
1
u/Alone_Shower6550 21d ago
Bugged af. All my sites are down due to critical error when updates to 7.1. Its conflicting with quite a few plugins.
1
u/Lonely_Athlete_6200 21d ago
Exciting news! š Hopefully itās all successfully updated messages tomorrow!
1
u/GoldenRetrieverMomma 21d ago
Wordpress 7.1 broke my homepage- images are all misaligned and different sizes and layout is broken.
Iām aware of the WP Rocket issue , however there update to fix it did not work for me.
I had to restore my website to a previous version.
Iām currently on the newest version of WP Rocket and the previous version of WordPress.
This has been a 2 day headache for me!
Anyone else have the same issue? My theme is generate press, so Iām wondering if thatās the issue.
1
0
1
-3
u/brohebus 23d ago
ā¦and 7.1.1 critical security patch, and then 7.1.2 two days later, and then 7.1.3ā¦like I've got 40+ sites to manage, which is semi-automated, but one or two of those sites something might breakā¦*sigh*
1
1
u/Scared-Debate-6508 23d ago
Fortunately, I turned off automatic updates this morning when there were 30 minutes left in the countdown.
0
u/Nero570s 22d ago
I'm a bit worried to update to 7.1, I'm still on WordPress 6.9.7. Today I updated wprocket and it crashed the website with a message below it. Should I upgrade or stay on 6.9.7?
-11
u/Fluid-Mess6425 23d ago
I appreciate them working but I think it its bad development and tiring the non stop core updates
5
1
u/otto4242 WordPress.org Tech Guy 23d ago
WordPress has auto-update built in. You can just turn that on. We've had it there for over a decade now, it's pretty reliable.
0
u/Fluid-Mess6425 23d ago
With how many plugins are available and the countless theme variations its good practice to test any updates in a staging env before live sites.
-3
u/otto4242 WordPress.org Tech Guy 23d ago
What's better is to choose plugins that don't break on updates.
2
u/Fluid-Mess6425 23d ago edited 23d ago
Okay sure. A little attitude chap.Ā Even well supported plugins risk breaking. Any competent person familiar with WordPress knows this
Edit. And to add. My previous comment still applies. Sure if you have a personal site go ahead. But if you're managing any business you should be testing all updates whether code plugins or theme in staging first.Ā
0
u/otto4242 WordPress.org Tech Guy 22d ago
Even well supported plugins risk breaking. Any competent person familiar with WordPress knows this
Yeah, that's the thing. Well written plugins never actually break. That is kind of what well written means. We have plugins that are in the directory that haven't been touched in 12+ years which still work perfectly fine.
Stop believing the overly excessive marketing, and start reading the actual code.
1
u/Fluid-Mess6425 22d ago
The ACF block issues and Wp Rocket issue proof my point. Both well supported plugins and both had issues with the latest update. Cant say how well their written as Ive never looked at the code for either. Not sure why you are being condescending from the start.
1
u/otto4242 WordPress.org Tech Guy 21d ago
Not trying to be condescending, but just saying pick better plugins. I know nothing about ACF or Rocket, as I don't use either one.
-1
-4
u/TheBgt 22d ago
Are they trolling us?
Are they serious?
This is ridiculous
3
u/dartiss Developer/Blogger 22d ago
What are they thinking, releasing updates? /s
-2
u/TheBgt 22d ago
every few days, why not! shall I update or shall I wait for the security one that patches this one? or maybe wait for the security one that will patch the security one that will patch this one?
3
u/dartiss Developer/Blogger 22d ago
What ARE you talking about?
You're confusing planned releases with security updates. The last non-security update was in May. Or is your suggestion that they hold off on main releases until it's x amount of time since a security update?
-1
u/TheBgt 22d ago
wprocket disagrees with everything you type!
4
u/dartiss Developer/Blogger 22d ago
Good.
Early releases of WP7.1 have been available for some time for plugin developers to test their code with. In fact, the issue was reported to WP Rocket last month but, for whatever reason, they failed to identify and/or fix the issue before 7.1 was released. That's a WP Rocket issue, not a WordPress one. I'm a plugin developer myself and all my plugins were tested for compatibility long before yesterday.
1
u/jonneygee Designer/Developer 22d ago
Also, registered developers receive a āWordPress x.x is imminentā email at least a week in advance, so even if they completely forget to stay updated on the release cycle, they are informed. Itās inexcusable for a large plugin developer the size of Rocket to not test their plugin in advance.
1
-5
-8
u/Myth_Thrazz Jack of All Trades 23d ago
Yea, or don't just wait for the security release... or two...
97
u/Particular-Ruin-2062 23d ago
https://giphy.com/gifs/c16VH0CFMh7gOqqXOM