WordPress is among the most popular technologies for creating and hosting websites and potentially one of the most influential platforms on the internet. This popularity and influence of WordPress and its founder, Matt Mullenweg is seriously at stake now amidst a controversy that includes a leading WordPress hosting service, WP Engine. 

What started as a legal battle has now turned into a bitter feud and public spectacle involving lawsuits, mean tweets, and controversial website changes. 

In this guide, we will dissect the drama to provide you with a comprehensive overview of the situation. We explore both sides of the argument and the potential implications for the WordPress community. 

WordPress recently “forked” a WP Engine plugin, basically removing and replacing the plugin with its own version. This has raised some serious concerns about WordPress and its CEO Matt Mullenweg and the way they handle brands associated with them. 

We have more in this update below:

Update Oct 12: WordPress.org Takes Over WP Engine Plugin

WordPress.org founder Matt Mullenweg announced that they are forking a plugin developed by WP Engine. This seriously blows WP Engine due to their dispute with Matt Mullenweg, which included multiple lawsuits and unsavory tweets from both parties. 

“Advanced Custom Fields” is a WordPress plugin designed by WP Engine to help users customize their edit screens. It has been replaced by a new plugin from WordPress called Secure Custom Fields. The URL for Advanced Custom Fields is still active, but it features the new “forked” plugin.

Source: WordPress.org

To simplify the above statement, WordPress just removed a plugin from its directory (WP App Store) and replaced it with a forked plugin (a copy of a modified plugin) of its own. This is similar to Apple replacing the Spofity on its app store with a modified version of Apple Music because of a dispute. 

However, WordPress and its CEO, Matt Mullenweg, have the right to do so as per their plugin directory guidelines. Mullenweg states his reason for the change is "to remove commercial upsells and fix a security problem." 

WP Engine deemed this action unethical because the change was made without the developer's consent. 

Mullenweg and his team have issued several replies stating that "incidents like this have occurred in the past" and that "This is a rare and unusual situation brought on by WP Engine's legal attacks; we do not anticipate this happening for other plugins."

X users are upset with WordPress over this decision (which seems like a personal attack).

Source: X

People are also not happy with how WordPress handled the situation on a public platform like X.

Source: X

WordPress users are just as upset. The newly forked Secure Custom Fields app is receiving hundreds of one-star reviews. 

Source: WordPress.org

When the situation changes, we will update you further on the feud between Matt Mullenweg's WordPress and WP Engine. 

You can learn more about the disputes between Matt Mullenweg and WP Engine below. There is a lot to unpack here, so we tried our best to condense the information into a short post. 

Let's start with what WordPress is and why it is in conflict with WP Engine.

The Genesis of WordPress and Automattic

WordPress is an open-source tool for developing websites, founded in 2003. It is built on PHP and jQuery and powers over 40% of websites on the Internet. 

At the center of WordPress's success story is its vast ecosystem of plugins and themes, which is accessible through an app store-style marketplace. The WordPress platform and its plugin/theme store make it accessible for both programmers and regular users (with little experience) looking to build almost anything. 

WordPress is licensed under the GNU General Public License (allows users to modify, share, and use software for free). This allows for modification and commercial use, provided that derivative works maintain the same license. 

The WordPress name and logo are trademarks owned by the WordPress Foundation, a charitable organization created by Matt Mullenweg. They require explicit permission to use in any project or product.

Matt Mullenweg is also the CEO of Automattic, a multi-billion dollar company that offers hosting services through WordPress.com, WordPress's commercial brand.

Automattic vs. WP Engine: The Conflict Begins

There's a history of bad blood between the WordPress/Automattic brand and WP Engine. But things started to take a serious turn recently in September when Automattic issued a trademark license agreement to WP Engine. 

The agreement states that WP Engine will have to pay 8% of its gross revenue to Automattic. This will result in WP Engine having to fork over millions of dollars to Automattic monthly. Ruby on Rails creator David Heinemeier Hansson claims that Automattic's action is a violation of open-source software principles.

Automattic and Matt Mullenweg's gripe with WP Engine is multifaceted:

1. Lack of Contributions: WP Engine profits off WordPress immensely while not contributing towards WordPress.org (the non-profit arm of WordPress).
2. Trademark Misuse: WP Engine allegedly misuses the WordPress trademark. Their payment plans look like WordPress products, which can be misleading.
3. Ecosystem Degradation: WP Engine is accused of forking and rebranding WordPress open-source plugins like WooCommerce. They charge users a fee but deliver a subpar experience.

WP Engine didn't agree to these terms as 8% of gross income (before taxes and expenses) can potentially cripple the company. Especially if WP Engine is stripped of its ability to earn an income through its WordPress plugins. 

WP Engine is also not in agreement with the above 3 allegations that Mullenweg has made towards them. 

WP Engine rejected the above terms shortly after Matt Mullenweg publicly labeled them a "cancer to WordPress" during his keynote address at the Worldcamp US conference. 

These bold actions and statements marked the beginning of a series of actions that would further escalate the feud between Automattic and WP Engine.

Legal Skirmishes and Public Repercussions

WP Engine did not like the accusations made against them. Most noteabley the harsh words from Mullenweg's keynote. Remember? "WP Engine is a cancer to WordPress."

This led WP Engine to retaliate against Automattic by issuing a cease-and-desist letter accusing Mullenweg of "salacious and outrageous statements."

Automattic then responded with their own cease and desist letter to WP Engine demanding that they stop the unauthorized use of WordPress trademarks. 

After some aggressive tweets from both parties, the situation took a horrible turn for WP Engine as they were banned from WordPress.org. This action impacted developers and users by restricting access to plugins and updates within the WordPress repository. 

Mullenweg's public stance and media appearances added more fuel to the fire. He appeared on streams like The Primagen and Theos, arguing his position. These actions resulted in WP Engine filing a lawsuit citing Mullenweg's appearances as evidence. 

The lawsuit includes allegations ranging from Computer Fraud and Abuse Act violations to attempted extortion and unfair competition.

The Checkbox Controversy

A bold yet bizarre twist in this saga took place with the introduction of a new login checkbox on WordPress. The checkbox states, "I am not affiliated with WP Engine in any way, financially or otherwise."

Users were blocked from logging into WordPress if they did not agree to the statement. WP Engine quickly clarified that their customers and users are not affiliates, but the damage was already done. 

This move has driven many in the community to contemplate forking WordPress. However, this can be a challenging and complex process. 

Perhaps these users can switch over to a new platform?

Community Reactions

The WordPress community is polarized by this drama between WP Engine and Automattic. While some support Mullenweg's stance against WP Engine, others are appalled by what they see as his autocratic behavior. 

Automattic even offered a severance package to employees who disagreed with its stance, and 159 employees—8.4% of its staff—took the deal.

Automattic even offered a severance package to employees who disagreed with its stance, and 159 employees—8.4% of its staff—took the deal.

Despite the turmoil, some back Mullenweg, believing that protecting WordPress from exploitation by private equity firms like Silver Lake is crucial. On the other hand, critics argue that Mullenweg's actions are more about asserting control than safeguarding the ecosystem.

Update: People are even more upset with Automattic, especially Matt Mullenweg after they decide to take over the Advanced Custom Fields plugin. We have included screenshots from users at the start of this article.

Even users who previously understood Mullenweg's stance on this situation are now unhappy with his aggressive approach to dealing with this situation.

The Bigger Picture: Open Source and Corporate Interests

This conflict is a stark reminder of the inherent tensions between open-source ideals and corporate interests. WordPress has thrived because of its open-source nature, allowing a vast community to modify and extend the platform. 

However, monetizing open-source projects without compromising their core values is a delicate balancing act.

While Automattic has played a significant role in WordPress's growth, WP Engine has also contributed to its widespread adoption by offering robust hosting solutions. The current dispute highlights the challenges of sustaining an open-source project when significant financial interests are at stake.

TL;DR: WordPress vs WP Engine

• WordPress vs WP Engine drama involves legal battles, lawsuits, and public disputes.
• In a recent development, WordPress "forked" WP Engine's Advanced Custom Fields plugin, replacing it with Secure Custom Fields.
• WP Engine claims the move was unethical; WordPress defends it as necessary for security.
• Tensions escalated due to Matt Mullenweg's accusations and a licensing fee demand of 8% of WP Engine's revenue.
• WP Engine rejected the terms, leading to cease-and-desist letters and a lawsuit.
• The WordPress community is divided, with some supporting Mullenweg's actions and others criticizing his approach. However, more users have moved against Mullenweg's actions after the recent forking of the WP Engine plugin.
• Conflict underscores the tension between open-source ideals and corporate interests.

Leah Gianna