WordPress Community Reacts To 6.0 Arturo
WordPress 6.0 Arturo received a generally positive response, with some unexpected experiences and responses.
Many users have been very positive about WordPress 6.0, and the feedback seems to be that 6.0 will receive a smooth rollout. Although there were some reports of plugin conflicts, overall opinions differed depending on who responded.
More than 36% of All Sites Last Updated
According to WordPress documentation, 36.2% have updated their WordPress sites within two weeks after the release of WordPress 6.
Nearly 20% of WordPress users still use version 5.9 of WordPress.
WordPress 6.0 Arturo refers to a version change. This means it is moving from the 5.x development branch into the 6. x branch.
Some users might find this scary, as a significant version change, such as a new cell phone model, can often mean radical changes.
WordPress 6.0 is different.
Version 6.0 is an incremental update, just like previous versions. It aims to make creating websites more accessible and more intuitive.
Some users will hesitate to update, but this is not necessarily bad.
Advanced WordPress Users
The Advanced WordPress Facebook group is made up of developers. There was a general acceptance of Gutenberg’s incompatibility. Some expressed that Gutenberg would be more stable and robust before adopting it for their clients.
One member of a 107 discussion about WordPress 6.0 commented on the insufficient documentation. This criticism is valid.
The over 100 comments about WordPress Arturo posted in this Facebook group reflect the consensus that WordPress Arturo is a positive step forward and acknowledges the vital progress made in 6.0.
One group member appreciated the Block Tree updates, while another stated that the editor felt smoother.
The editor’s smoothness is an interesting observation, as WordPress 6.0 aimed to make it easier to use.
Advanced Users, WordPress 6.0
Matt Cromwell is an Admin in the Advanced WordPress Facebook Group and a WordPress entrepreneur. He shared his thoughts about the reception of WordPress 6.0.
He frames WP 6.0's reception around how it was received.
“WordPress 6.0’s primary goal was to improve Full Site Editing to make WordPress more accessible and attractive for WordPress implementers. These could be freelance developers, agencies, or internal web development teams.
WordPress’ future is complete site editing, but it will only gain traction if it succeeds.
Entire Site Editing will only gain traction if the themes support it. This feature is currently only available to users if your themes support it.
Full Site Editing is now more potent than ever for theme authors thanks to new features such as style switching, page templates, and integrated block patterns.
This will in theory improve adoption over the long term.
Concerning community reception, the response of small businesses, freelancers, and agencies to Full Site Editing is very similar to the time Gutenberg was first introduced. It is too young to be able to create sites with it currently.
People see the potential. However, if you wish to offer clients a feature that allows them to make site-wide changes, Elementor and Divi are more mature and battle-tested.
This is evident in the Gutenberg discussion boards, where there has been a lot of public discussion about making the board more “agency-friendly”.
The feedback and the proposed improvements are constructive in understanding how implementers struggle to adopt all that Gutenberg had to offer.
Reaction at Reddit
Reddit’s reaction was more opinionated than the Advanced WordPress Users Facebook group discussions.
One member, sdenike, wrote that they were content using the Gutenberg editor:
“I’ve been using Gutenberg as my only editor for over a year and haven’t had any of the problems/qualms other people have experienced on their sites …”.
However, the comment received many responses. One member observed that WordPress had become worse.
Why would anyone say that the new WordPress core version is better than the old version?
WP 6.0 was thoroughly tested by members of the WordPress community before release. This does not mean that WordPress has shipped an inferior product.
An update may be perceived as more dangerous than it is because of a conflict between an older plugin or theme.
Although 6.0 was designed to be backward-compatible, there are bound to be conflicts with plugins or themes.
It is a good idea to ensure all themes and plugins are up-to-date before blaming the WordPress core.
Possible Theme and Plugin Conflicts
Redditor afr0flava posted a bizarre bug that rendered a blank screen for editing.
“My “edit page” page on Chrome is now blank since the update, urrgh!”
Another Redditor, laser point, commented on how the justified alignment was changed after the update.
“I only want Justified alignment in text and paragraph. “Why was it removed?”
Redditor arose to ask a question regarding decreased performance following WordPress 6.0.
“Hi, I’m using WordPress 6.0. I want to find out why my website isn’t performing well. I enabled debug in WordPress 6.0 and found something (missing PHP library).
The user explained that their client site was working fine but slowing down and needed assistance identifying the plugin conflicting with the latest version of WordPress.
Possible bug in WordPress 6.0?
Redditor Another brought up an interesting problem (and possibly isolated) regarding content alignment.
StinkyWeezle commented.
It’s great, but my column containers are now vertically centered by default, with a gap of 2em between them.
The fallbacks were updated if you did not set a vertical alignment. However, they will still appear top-aligned in the editor until you click each block.
Now I must upgrade 150 sites to ensure that there is a “not hacking core” solution to the fallbacks.
Gutenberg Still Has Holdouts To Editor
As mentioned above, nearly 20% of WordPress users have not upgraded to WordPress 6.0.
Reddit’s recent thread may partly explain this.
Redditor prankster999 favored Gutenberg over the classic editor. They didn’t elaborate on why they preferred the classic editor to Gutenberg.
prankster999 posted:
“Am I the only individual who prefers the “Classic editor” to the “Block Editor”?
I understand that the Block Editor tries to make WordPress look more like Medium.
The “Classic Editor” is more traditional and can be found on websites such as Reddit or forums (like Xenforo).
Others, such as Rockycse21, agree, noting the classic editor is more “reliable”.
Although they didn’t elaborate on what reliable meant, it could be understood as a comment about Gutenberg’s unfinished product. Gutenberg doesn’t have the same familiarity and behavior as the Classic Editor.
Some people may be reluctant to upgrade because they feel secure in what they have. It’s not worth fixing what’s broken.
Redditor Picard102 shared their opinion about Gutenberg’s dislike among many users:
“You are not the only one. Many people hate the Block Editor.
This is an extreme opinion, but it’s not unusual. It is still challenging to adopt Gutenberg.
Higgs – B observed Gutenberg editor was not fully ready yet, which is also true.
“Unfortunately, the block/Gutenberg editor is not yet mature enough for non-coders.”
WordPress 6.0
It is primary to note that the latest WordPress version is an incremental update, not a significant update. It is also sketch to be compatible with older versions. It will work in server environments with PHP versions lower than 7.4 (down from PHP 5.6), but PHP 7.4 is the recommended minimum.
It is important to remember that WordPress 6.0, like 5.9 offers beta support for PHP 8.0.
Users who have upgraded to PHP version 8.2 may experience incompatibility problems.
It is a good idea to backup your entire WordPress website and database before you update. This will allow you to restore the site to its original state if something goes wrong.
It is possible to stop some of the weirdness and bugs that users report by knowing these things before using them.
WordPress 6.0 was generally received well by the WordPress community.
