WordPress 6.4.1 Maintenance Release Fixes Bugs In Version 6.4

0
569
WordPress Open Source Governance Faces Backlash After Official Account Trolling of FAIR Decentralisation Project
An official WordPress.org X (formerly Twitter) account has sparked backlash across the open-source community after posting a mocking, sarcastic comment targeting the FAIR (Federated And Independent Repositories) Project, an open-source initiative focused on decentralising WordPress plugin and theme distribution. The post was widely condemned by developers and contributors as “childish,” “unprofessional,” and “undignified,” with many arguing that the tone was inappropriate for an official channel representing one of the world’s largest open-source platforms. Several critical responses were later hidden by WordPress, further intensifying concerns around leadership and transparency. FAIR was launched in 2025 to address risks associated with centralised control over WordPress software distribution. The initiative emerged after Matt Mullenweg and Automattic cut off WP Engine from updating its plugins, disrupting thousands of WordPress sites and exposing vulnerabilities in the existing ecosystem. FAIR aims to prevent any single individual or organisation from disrupting the free distribution of WordPress software by establishing a vendor-neutral, federated infrastructure. The project has received backing from the Linux Foundation, which stated in June 2025 that vendor-neutral package management is critical infrastructure for modern content, e-commerce, and AI-driven systems, promoting innovation and protecting business continuity. The controversy was triggered after a WordPress user shared an update issue linked to FAIR Connect version 1.2.2 on X. While the issue required some users to perform manual updates, release notes clarified that it stemmed from a previously fixed error and was not representative of the project’s broader goals. Community figures, including SEO consultant Jono Alderson, criticised the official WordPress account’s conduct, warning that such behaviour undermines trust, damages the WordPress brand, and runs counter to open-source values of professionalism, neutrality, and inclusivity.

WordPress 6.4.1- uncovering critical bug fixes and their broader implications, offering users insights on navigating tech’s unpredictability.
WordPress users can breathe a sigh of relief as a maintenance release, version 6.4.1, has been swiftly rolled out to address critical issues that emerged shortly after the release of WordPress 6.4 on Tuesday, November 7th.
This new maintenance release comes as a lifesaver for users who encountered several bugs, with two of them having significant implications for the functionality of certain plugins, potentially wreaking havoc on affected websites. In the spirit of transparency, we break down the issues and their fixes in reverse pyramid style.
Critical Bug Causes Download to Fail
The most pressing issue addressed by WordPress 6.4.1 was a critical bug that caused users to encounter download failures, displaying a disheartening error message – “cURL error 28: Operation timed out.”
The root of this problem can be traced back to a major change in WordPress 6.4, specifically an update to the Requests library version. This update included a breaking change for users on hosts with curl version 7.29 or older, which was, unfortunately, more common than expected. The latest cURL version is 8.4.0, highlighting the need to stay up to date.
Backward Compatibility Bug
Another critical issue stemmed from the removal of code that was no longer used by the WordPress core, an action taken in an attempt to streamline and optimize the platform. However, the removal of this code inadvertently disrupted various plugins that still relied on it. The consequences of this action were far-reaching, causing a myriad of issues for users and their websites.
The solution provided by WordPress 6.4.1 was to reintegrate the removed code, ensuring that backward compatibility was maintained and that plugins could function without hiccups.
Typo In Code – Minor Cosmetic Issue
The final issue tackled by this maintenance release was relatively minor in comparison but still noticeable. A typographical error affected the appearance of a nag screen in the administrator panel, causing it to stretch awkwardly across the top of the page.
This typo was rectified with the release of WordPress 6.4.1, restoring the aesthetic integrity of the user interface.
The swift response by WordPress to address these issues exemplifies their commitment to improving the user experience and ensuring a seamless transition to new versions of the platform. While test versions are made available to the community for feedback and error reporting, some issues inevitably surface with the final release, as was the case with WordPress 6.4 codenamed Shirley.

LEAVE A REPLY

Please enter your comment!
Please enter your name here