WordPress Releases 6.6.1 To Fix Fatal Errors In 6.6 via @sejournal, @martinibuster

1 month ago 29

ARTICLE AD BOX

WordPress 6.6.1 fixes important errors from past week's 6.6 - This is wherefore you should update now

WordPress releases 6.6.1 to corrects large flaws detected successful mentation 6.6

A week aft releasing the troubled mentation 6.6, WordPress has released different mentation that fixes 7 large issues including 2 that caused fatal errors (website crashes), different contented that caused a information plugins to contented mendacious warnings positive respective much that created unwanted UI changes.

Fatal Errors In WordPress 6.6

The 1 contented that got a batch of attraction connected societal media is 1 that affected users of definite leafage builders and themes similar Divi. The issue, portion comparatively minor, dramatically changed the look of websites by introducing underlines beneath each links. Some connected societal media joked that this was a hole and not a bug. While it’s a mostly a bully idiosyncratic signifier to person underlines beneath links, underline aren’t indispensable successful each links, similar successful the top-level navigation.

A post connected the WordPress.org enactment forums was the archetypal noticeable indications successful societal media that thing was incorrect with WordPress 6.6:

“Updating to 6.6 caused each links to beryllium instantly underlined connected a staging divi themed site.”

They outlined a workaround that seemed to alleviate the contented but they were unsure astir what the basal origin of the occupation was.

They past posted:

“But does anyone deliberation this means I inactive person thing incorrect with this staging site, oregon is this a WordPress mentation update issue, oregon much apt a divi taxable contented I should talk to them about? Also, if anyone is adjacent acquainted with expected Rparen error…that I’m conscionable riding with astatine the moment, that mightiness help. Thanks.”

Divi issued an exigency hole for that their users could use adjacent though the contented was connected the WordPress side, not connected the Divi side.

WordPress aboriginal acknowledged the bug and reported that they volition beryllium issuing a hole successful mentation 6.6.1.

The Other Issues Fixed In 6.6.1

Fatal Error

is_utf8_charset() undefined erstwhile called by codification successful compat.php (causes a fatal error).

A conception of codification successful 6.6 caused a captious contented (fatal error) that prevents the website from functioning normally. It was noticed by users of WP Super Cache. WP Super Cache developed a impermanent workaround that consisted of wholly disabling the website caching.

Their notation successful GitHub stated:

“Disabling the cache removes the mistake but is acold from ideal.”

Php Fatal Error

“PHP Fatal error: Uncaught Error: Object of people WP_Comment could not beryllium converted to string.”

There was a occupation with a portion of the WordPress codification wherever 1 portion was trying to get the sanction of the idiosyncratic who near a remark connected a post. This portion of the programme was expected to person a fig (the remark ID) but sometimes it was getting a much analyzable portion of accusation alternatively (a WP_Comment object) which past triggered a PHP “fatal error.” An analogy mightiness beryllium similar trying to acceptable a quadrate peg into a circular hole, it doesn’t work.

This contented was discovered by idiosyncratic who was utilizing the Divi website builder.

The different bugs that are fixed didn’t origin websites to clang but they were inconvenient:

Read the afloat details of WordPress 6.6.1 attraction release:

WordPress 6.6.1 Maintenance Release

Featured Image by Shutterstock/HBRH

SEJ STAFF Roger Montti Owner - Martinibuster.com astatine Martinibuster.com

I person 25 years hands-on acquisition successful SEO and person kept on apical of the improvement of hunt each measurement ...