[ad_1]
Every week after releasing the troubled model 6.6, WordPress has launched one other model that fixes seven main points together with two that prompted deadly errors (web site crashes), one other concern that prompted a safety plugins to concern false warnings plus a number of extra that created undesirable UI adjustments.
Deadly Errors In WordPress 6.6
The one concern that received quite a lot of consideration on social media is one which affected customers of sure web page builders and themes like Divi. The difficulty, 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 typically consumer apply to have underlines beneath hyperlinks, underline aren’t crucial in all hyperlinks, like within the top-level navigation.
A post on the WordPress.org assist boards was the primary noticeable indications in social media that one thing was improper with WordPress 6.6:
“Updating to six.6 prompted all hyperlinks to be instantly underlined on a staging divi themed web site.”
They outlined a workaround that appeared to alleviate the difficulty however they have been uncertain about what the foundation reason behind the issue was.
They then posted:
“However does anybody assume this implies I nonetheless have one thing improper with this staging web site, or is that this a WordPress model replace concern, or extra doubtless a divi theme concern I ought to communicate to them about? Additionally, if anybody is even aware of anticipated Rparen error…that I’m simply driving with in the mean time, which may assist. Thanks.”
Divi issued an emergency repair for that their customers might apply though 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 Mounted 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 prompted a essential 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 short lived workaround that consisted of utterly disabling the web site caching.
Their notation in GitHub said:
“Disabling the cache removes the error however is way from preferrred.”
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 identify of the one that left a touch upon a submit. This a part of this system was imagined to obtain a quantity (the remark ID) however generally it was getting a extra complicated piece of knowledge as an alternative (a WP_Comment object) which then triggered a PHP “deadly error.” An analogy may 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 can be mounted didn’t trigger web sites to crash however they have been inconvenient:
Learn the total particulars of WordPress 6.6.1 upkeep launch:
WordPress 6.6.1 Maintenance Release
Featured Picture by Shutterstock/HBRH
[ad_2]
Source link
