WordPress 6.0 has been well received by many users and the feedback regarding 6.0 seems to be one of smooth rollouts. There have been some reports of plugin conflicts, but overall, opinions seem to differ depending on which part of the WordPress community is responding.
Over 36% of all sites updated
According to WordPress documentation, 36.2% of all WordPress sites to date have been updated within two weeks of the release of WordPress 6.0.
About 20% of the user base is still using version 5.9 of WordPress.
Source: WordPress.orgWordPress 6.0 Arturo is a version change. That is, updating from the 5.x development branch to the 6.x branch.
A version change for most things, such as a new phone model, usually means a radical change, so it might seem scary to some users.
But that’s not the case with WordPress 6.0.
Like previous version updates, version 6.0 represents an incremental update that can be described as focused on making the website creation experience more intuitive and accessible.
That said, some users are bound to be wary of updates, and not without good reason.
Advanced WordPress User
In the Advanced WordPress Facebook group, whose members are developers, the general tone of the discussion was pragmatic acceptance that Gutenberg wasn’t ready yet. Release until Gutenberg is more robust and stable before adopting that platform to clients.
In a discussion of 107 posts about WordPress 6.0, one member commented on the lack of adequate documentation, which is a valid criticism.
Of the over 100 comments posted, WordPress Arturo in this Facebook group acknowledged significant progress in 6.0 and is a step forward.
One member of the group praised the block tree updates, while another said the editor felt smoother overall.
This last observation about editor smoothness is interesting because one of the goals of WordPress 6.0 was to make it more intuitive to use.
Advanced users and WordPress 6.0
Matt CromwellAdmin of the Advanced WordPress Facebook group, WordPress entrepreneur, and co-founder of GiveWP.com, shared his thoughts on WordPress 6.0 acceptance.
He frames the reception on what WP 6.0 has to offer and how it has been received.
“The main goal of WordPress 6.0 is to enhance site-wide editing capabilities to make it more accessible and attractive to WordPress implementers: freelance developers, agencies, or in-house web development teams. was to do
Full site editing is the future of WordPress, but only if it gets noticed.
The only way Full Site Editing gets real traction is if the theme embraces it. This feature is currently only available to users if their theme declares support for it.
New features such as style switching, page templates, and integrated block patterns make full site editing more powerful for theme authors.
So ideally this will help improve recruitment in the long run.
As for community reception, among the small businesses, freelancers, and agencies I regularly interact with, their reaction to a full site edit has been very similar to when Gutenberg was first introduced. Similar. I’m too immature to build a site right now.
All in all, people see the potential, but if you want to give your clients the ability to make dramatic site-wide changes, other tools like Elementor and Divi have already received far more testing. matured.
A really good example of this is the public discussion going on on Gutenberg’s discussion board about being more “agency friendly”.
Both the suggested improvements and the feedback are very enlightening in understanding how implementers are approaching adoption of all that Gutenberg currently has to offer. ”
Reactions on Reddit
Reactions on Reddit were more divided than conversations in the private Advanced WordPress Users Facebook group.
One member named sdenike posted that she is happy with the Gutenberg editor.
“I’ve been using Gutenberg as my sole editor for over a year now and have never had the problems or anxieties other people have had with their sites…”
That comment, however, was met with responses expressing opposing experiences: one member observed that WordPress had deteriorated.
Why is someone saying that new versions of WordPress core are worse than previous versions?
WP 6.0 was tested by many members of the WordPress community before its release, so it’s not because WordPress shipped a bad product.
Perceptions of bad updates are very likely due to conflicts with outdated plugins or themes.
6.0 is designed to be backwards compatible, but conflicts with plugins and themes are almost inevitable.
So it’s a good idea to make sure all your plugins and themes are up to date before blaming WordPress core.
Possible plugin and theme conflicts
Redditor afr0flava posted about a strange bug rendering a blank page on the edit screen.
“Since the update, my Edit Post page is blank in Chrome.
Another Redditor, laserpoint, commented on how the justified placement is different after the update.
“Justified alignment of text and paragraphs required. Why was it removed?”
In another discussion, a Redditor asked about slow performance after updating to WordPress 6.0.
“Hi, I’m using WordPress 6.0 and I’m trying to investigate why my website isn’t working. I enabled debugging in wp-config.php and found something (PHP missing library)”
The user states that the client site is working fine except for the slow performance and needs help identifying a plugin that conflicts with the new version of WordPress. explained in detail.
Potential bug in WordPress 6.0?
Another Redditor is interesting (and apparently isolated) content placement issues.
Member StinkyWeezle commented:
“This is great, but all my column containers are vertically centered by default with a 2em gap between them.
If you don’t set the vertical alignment, all fallbacks have changed, but each block will still appear aligned on top in the editor until you click on it.
Rock 150 sites will need to be upgraded until a “don’t hack the core” fix is found to change the fallback. ”
Gutenberg still faces holdouts to classic editors
As mentioned above, nearly 20% of WordPress users have not yet migrated from 5.9 to 6.0.
A recent thread on Reddit may partially explain why.
A Redditor named prankster999 has expressed a preference for the traditional editor over Gutenberg. They didn’t explain why the non-classic editor was so familiar.
Posted by prankster999
“Am I the only one who prefers the ‘Classic Editor’ over the ‘Block Editor’?
We understand that “Block Editor” tries to make WordPress look and function closer to Medium.
But the “classic editor” is more traditional for websites like Reddit and forums (such as Xenforo). ”
Others, like rockycse21, agreed, pointing out that the traditional editor is “more reliable”.
They didn’t explain what they meant by reliable, but a comment about the classic editor being a finished product that works as expected while Gutenberg isn’t finished yet, and doesn’t provide any sense because of its newness. can be interpreted as Familiarity provided by the Classic Editor.
So the feeling of being comfortable using what you already have might explain some of your reluctance to upgrade. Why fix what isn’t broken?
Redditor picard102 opined that many users actively dislike Gutenberg.
“You are not alone. There are many people who despise block editors.”
It’s a bit extreme, but not an uncommon opinion. Resistance to adopting Gutenberg continues.
Higgs-B observed that the Gutenberg editor is not yet fully ready, and this is true.
“Unfortunately, the Block/Gutenberg editor is not mature enough for non-coders.”
WordPress 6.0
The most important thing to remember about the latest version of WordPress is that it’s an incremental update, not a radical one. It is also designed to be backward compatible. This means that although the minimum recommended version is 7.4, it will also work in server environments using PHP versions below 7.4 (up to PHP 5.6).
An important thing to consider is that WordPress 6.0, like 5.9 before it, currently only offers beta support for PHP 8.0.
Users updating to PHP version 8.0 may encounter incompatibility issues.
Before updating, we recommend backing up your entire WordPress site and database so that you can restore your website to its previous state if something goes wrong.
Knowing all of these things up front may save you from having to go through the bugs and oddities some users are reporting.
Overall, the response from the WordPress community to WordPress 6.0 was that it was a smooth update.
