WordPress.org Takes Control of WP Engine Plugin

WordPress.org has recently taken control of a well-known WP Engine plugin with the aim of eliminating commercial upsells and addressing a security issue, as announced by Matt Mullenweg, WordPress cofounder, and CEO of Automattic. This initiative involves a “minimal” update to the Advanced Custom Fields (ACF) plugin, now known as “Secure Custom Fields.”

The specific security issue referenced by Mullenweg remains unclear in his post. He mentions invoking point 18 of the plugin directory guidelines, allowing WordPress to take actions such as removing or modifying a plugin without the developer’s consent. Mullenweg links this decision to a lawsuit filed by WP Engine against him and Automattic.

While past incidents of similar nature have occurred, the current situation is unique and driven by WP Engine’s legal actions. It is not anticipated to be a common occurrence with other plugins.

The ACF team of WP Engine asserts that WordPress has never forcibly taken control of a plugin without the creator’s consent. Non-WP Engine, Flywheel, or ACF Pro users are instructed to visit the ACF website for instructions on how to download the genuine 6.3.8 version to continue receiving updates.

The ACF plugin, as its name suggests, enables website creators to utilize custom fields when standard options are insufficient. This functionality, according to ACF, is already a native feature of WordPress that can be challenging to use.

Automattic, WordPress.org, and WP Engine have been contacted by The Verge for comments on this matter.

Update October 12th: Mullenweg’s use of the “fork” label has been clarified.

Impact of WordPress.org’s Acquisition

This section will discuss the implications of WordPress.org taking over the WP Engine plugin and the reasoning behind this decision.

Security Concerns Addressed

Explore the security issue highlighted by Matt Mullenweg and how the new “Secure Custom Fields” plugin aims to resolve it.

Legal Context

Details about the lawsuit filed by WP Engine against Mullenweg and Automattic, shedding light on the legal backdrop of the situation.

Community Response

Insights into how the community, especially ACF users, has reacted to this transition and the instructions provided by the ACF team.

Functionality of ACF Plugin

Highlight the purpose and benefits of the ACF plugin in enabling customization beyond standard WordPress features.

Seeking Industry Perspectives

Comments and viewpoints from industry experts and stakeholders on this unexpected development.

Conclusion

Summarize the key points discussed in the article regarding WordPress.org’s acquisition of the WP Engine plugin and its implications for the WordPress community.

FAQs

Q: Why did WordPress.org take over the WP Engine plugin?

A: The takeover was motivated by a desire to eliminate commercial upsells and address a security problem.

Q: How can users ensure they receive updates for the ACF plugin?

A: Non-WP Engine, Flywheel, or ACF Pro users should visit the ACF website and follow the provided instructions to download the genuine 6.3.8 version.

Credit: www.theverge.com