Per week after releasing the troubled model 6.6, WordPress has launched one other model that fixes seven main points together with two that brought about deadly errors (web site crashes), one other concern that brought about a safety plugins to concern false warnings plus a number of extra that created undesirable UI modifications.
Deadly Errors In WordPress 6.6
The one concern that received numerous consideration on social media is one which affected customers of sure web page builders and themes like Divi. The problem, whereas comparatively minor, dramatically modified the look of internet sites by introducing underlines beneath all hyperlinks. Some on social media joked that this was a repair and never a bug. Whereas it’s a usually an excellent consumer follow to have underlines beneath hyperlinks, underline aren’t needed in all hyperlinks, like within the top-level navigation.
A post on the WordPress.org help boards was the primary noticeable indications in social media that one thing was unsuitable with WordPress 6.6:
“Updating to six.6 brought about all hyperlinks to be instantly underlined on a staging divi themed website.”
They outlined a workaround that appeared to alleviate the difficulty however they had been uncertain about what the basis reason for the issue was.
They then posted:
“However does anybody assume this implies I nonetheless have one thing unsuitable with this staging website, or is that this a WordPress model replace concern, or extra probably a divi theme concern I ought to communicate to them about? Additionally, if anybody is even acquainted with anticipated Rparen error…that I’m simply using with for the time being, that may assist. Thanks.”
Divi issued an emergency repair for that their customers may apply regardless that the difficulty was on the WordPress aspect, not on the Divi aspect.
WordPress later acknowledged the bug and reported that they are going to be issuing a repair in model 6.6.1.
The Different Points Fastened In 6.6.1
Deadly Error
is_utf8_charset() undefined when known as by code in compat.php (causes a deadly error).
A piece of code in 6.6 brought about a important concern (deadly error) that forestalls the web site from functioning usually. It was seen by customers of WP Tremendous Cache. WP Tremendous Cache developed a brief workaround that consisted of utterly disabling the web site caching.
Their notation in GitHub acknowledged:
“Disabling the cache removes the error however is much from splendid.”
Php Deadly Error
“PHP Deadly error: Uncaught Error: Object of sophistication WP_Comment couldn’t be transformed to string.”
There was an issue with part of the WordPress code the place one half was attempting to get the title of the one that left a touch upon a submit. This a part of this system was presupposed to obtain a quantity (the remark ID) however generally it was getting a extra complicated piece of knowledge as a substitute (a WP_Comment object) which then triggered a PHP “deadly error.” An analogy could be like attempting to suit a sq. peg right into a spherical gap, it doesn’t work.
This concern was found by somebody who was utilizing the Divi web site builder.
The opposite bugs which might be fastened didn’t trigger web sites to crash however they had been inconvenient:
Learn the total particulars of WordPress 6.6.1 upkeep launch:
WordPress 6.6.1 Maintenance Release
Featured Picture by Shutterstock/HBRH
