WordPress vs. WP Engine Dispute Timeline

WordPress.org publishes a list of hosting companies offering deals to ex-WP Engine customers. The post cites "legal attacks" against Matt Mullenweg as the reason. Promoted hosts include Bluehost, Pressable, WordPress.com, and WordPress VIP. Offers range from free migrations to contract buyouts. This move directly encourages WP Engine customers to switch providers, further escalating the conflict in the WordPress ecosystem.

DHH acknowledges Mullenweg's removal of the controversial blog post, expressing approval of this decision. He publicly shares advice previously given in private, suggesting two key steps to resolve the conflict: returning the ACF plugin repository and abandoning the demand for a share of WP Engine's revenues. DHH emphasizes that open-source contributions should be voluntary and that while preventing trademark confusion is valid, it shouldn't require a paid license. This response offers a potential roadmap for de-escalation and highlights the ongoing debate about open-source business models and trademark issues in the WordPress ecosystem.

Hashim Warren reports on Twitter that the WordPress takeover of the Advanced Custom Fields (ACF) plugin is causing widespread site breakages. Warren shares multiple incidents of WordPress users experiencing problems after the unexpected change to this critical plugin, which is used on approximately 2 million live sites. The sudden implementation on a weekend has led to frustration among developers and site owners, with one user quoted as saying, "Thank you Matt Mullenweg for ruining my Sunday."

A Reddit user and WordPress developer, u/mccoypauley, posts on r/WordPress about losing a $40,000 contract for a website project due to the ongoing conflict between WordPress and WP Engine. The client reportedly pulled out of the contract and is reconsidering their CMS choice entirely. The developer also mentions other clients expressing concerns about WordPress's stability, potentially impacting future revenue.

Matt Mullenweg removes his initial response to DHH and publishes a new, more measured post. He apologizes for the original post's harsh tone, attributing it to recent personal attacks. Mullenweg reiterates key points about the dispute, emphasizing that the conflict with WP Engine centers on trademark abuse rather than GPL issues. He defends the ACF plugin takeover as a security measure and maintains that WP Engine and Silver Lake are the real antagonists in the situation. This revision attempts to address the backlash while still asserting Automattic's position in the ongoing conflict.

Matt Mullenweg publishes a blog post titled "Response to DHH," addressing David Heinemeier Hansson's criticism of Automattic's actions. The post takes a confrontational tone, questioning DHH's expertise and business acumen while defending Automattic's position on trademarks. Mullenweg's response receives significant backlash from the WordPress community for its personal attacks and confrontational nature. Following the negative reaction, Mullenweg removes the blog post.

DHH writes a blog post titled "Open source royalty and mad kings," further criticizing Matt Mullenweg's actions in the WordPress-WP Engine conflict. He focuses on the 8% revenue demand, the WordPress.org login oath, and the takeover of WP Engine's ACF plugin. DHH argues these actions breach open-source norms and set dangerous precedents, particularly warning against weaponizing open-source code registries. While acknowledging Mullenweg's contributions to WordPress, DHH urges him to reconsider his approach, emphasizing the potential damage to the broader open-source community.

WordPress.org assumes control of WP Engine's Advanced Custom Fields plugin, renaming it "Secure Custom Fields." Mullenweg cites security concerns and commercial upsells as reasons, invoking plugin directory guidelines. WP Engine contests this unprecedented action, advising users on accessing the original version. This move significantly escalates the ongoing conflict, directly affecting WP Engine's product offerings.

Scott Kingsley Clark, a prominent WordPress core contributor, announces his departure from the project. In a "Goodbye notice," Clark states he's terminating his core contributions and involvement with WordPress, citing his inability to continue making excuses for Matt Mullenweg's actions.

WordPress.org introduces a controversial login checkbox requiring users to confirm they're not affiliated with WP Engine. Mullenweg defends the action in WordPress Slack, suggesting WP Engine's lawsuit puts all .org participants at legal risk. The checkbox sparks heated discussions in the community, with WP Engine clarifying that customers and users are not considered affiliates.

David Heinemeier Hansson (DHH), the creator of Ruby on Rails, publishes a blog post titled "Automattic is doing open source dirty." He strongly criticizes Automattic's demand for 8% of WP Engine's revenues, calling it a "wanton violation of general open source ideals and the GPL license." DHH argues this action threatens the integrity of open-source licensing, potentially damaging the broader open-source ecosystem. He emphasizes that open-source licenses don't allow for arbitrary revenue demands based on a project's success. This critique from a prominent figure in the open-source community adds a new perspective to the ongoing WordPress dispute.

Approximately 159 Automattic employees (8.4% of workforce) accept a generous severance package, dubbed the "Alignment Offer." This move comes in response to internal disagreements over Mullenweg's handling of the WP Engine situation. The offer includes $30,000 or six months' salary, whichever is higher. Most departures (79.2%) are from Automattic's Ecosystem/WordPress areas. Mullenweg frames this as an opportunity to increase alignment within the company, despite the loss of talent. This event highlights internal tensions resulting from the ongoing WordPress ecosystem conflict.

Kellie Peterson, a former Automattic employee, publishes a Medium post exposing legal threats from Matt Mullenweg. Peterson had initially shared information about Automattic's staff buyout offer on social media. She reveals private messages from Mullenweg, accusing her of attacks and solicitation, and threatening legal action. Peterson defends her comments as legitimate commentary and criticizes Mullenweg's leadership style. This incident highlights growing tensions within the WordPress community and raises questions about Mullenweg's approach to criticism.

Automattic strongly refutes WP Engine's lawsuit, calling it baseless and meritless. They retain Neal Katyal, former Acting Solicitor General, as legal counsel. Automattic vows to vigorously defend against the suit and pursue all remedies against WP Engine. They reaffirm their commitment to protecting WordPress's integrity and democratizing publishing. This response intensifies the legal battle between the two companies in the WordPress ecosystem.

WP Engine sues Automattic and WordPress co-founder Matt Mullenweg, alleging extortion and abuse of power. The lawsuit claims violations of open-source promises and accuses Mullenweg of obscuring his control over WordPress entities. This legal action follows recent disputes over trademarks, temporary bans from WordPress.org resources, and rejected royalty proposals. The suit marks a major escalation in the ongoing WordPress ecosystem conflict.

WordPress.org temporarily lifts its ban on WP Engine until October 1. Mullenweg blames WP Engine's investor, Silver Lake, while expressing regret for customer impact. The lift allows sites to update plugins and themes, addressing security concerns. This occurs amid ongoing trademark disputes and community uncertainty about WordPress usage in services. The temporary nature of the lift suggests the conflict remains unresolved.

Pressable, owned by Automattic, starts ads aimed at worried WP Engine customers. They focus on update problems caused by WordPress.org's ban on WP Engine. This move shows how Automattic is trying to win over customers from its rival during the ongoing dispute.

WordPress.org bans WP Engine from accessing its resources. This prevents WP Engine customers from installing plugins or updating themes through WordPress.org. WP Engine calls it "unprecedented and unwarranted," while Mullenweg cites trademark violations and insufficient open-source contributions.

Automattic, led by Mullenweg, sends a cease-and-desist letter to WP Engine, alleging unauthorized use of "WordPress" and "WooCommerce" trademarks. Automattic claims exclusive commercial rights and accuses WP Engine of misleading consumers about their affiliation.

WP Engine sends a cease-and-desist letter to Automattic, demanding retraction of Mullenweg's critical comments. They accuse Mullenweg of making threats and false claims, including demands for large trademark payments. WP Engine defends its use of the WordPress trademark and denies wrongdoing.

Matt Mullenweg publicly criticizes WP Engine on multiple fronts. He accuses them of causing brand confusion, profiting without proper trademark licensing, and making minimal contributions to the WordPress community. Mullenweg also highlights WP Engine's practice of disabling the WordPress revision system, arguing it compromises a core feature and undermines user trust.

WP Engine secures a $250 million investment from Silver Lake, while Automattic exits its earlier investment. WP Engine reports over $100 million in annual recurring revenue and 75,000 global customers. This shift in investment marks a significant change in WP Engine's financial backing and corporate relationships, setting the stage for future developments in the WordPress ecosystem.

WP Engine secures $1.2 million in funding, with Automattic making a strategic investment. Automattic also launches its VIP Support for Web Hosts program, featuring WP Engine as the initial partner. This early collaboration highlights the once-positive relationship between the companies, contrasting with their current conflict.