WordPress vs. WP Engine Dispute Timeline

WP Engine's amended legal filing accuses Automattic and Matt Mullenweg of monopolization, illegal tying, trademark misuse, and deceptive practices. The 146-page document alleges years of intentional misrepresentation about ownership and risks of building on WordPress, aimed at misleading businesses and volunteers about its long-term safety.

The launch of the WP Engine Tracker site, showing customer departures, has sparked backlash. WP Engine alleges the site’s downloadable CSV file discloses private staging and development domains, not meant for public access, putting sensitive projects at risk. Users accuse Automattic of aggressive tactics, questioning the ethics of such data handling. The community's reaction highlights growing discontent with Automattic’s approach and concerns about potential privacy violations.

A report reveals that WP Engine neglected proper security vetting for a recently acquired plugin and did not fix a known vulnerability despite being notified over a month ago. The incident highlights ongoing concerns over the safety of WordPress plugins and the responsibilities of major hosting providers.

Following a brief downtime of WordPress.org, users quickly pointed out the irony, mocking Matt Mullenweg for his earlier taunts when WP Engine faced similar issues. The outage led to a wave of social media reactions, highlighting the double standard in Mullenweg’s criticism of competitors.

The founder of PatchStack has publicly disputed WordPress’s recent security assertions, which implied that plugins distributed outside the official WordPress repository are riskier. He argued that most vulnerabilities originated from .org plugins and suggested the claim lacked statistical backing. The debate adds to ongoing friction within the community over WordPress’s handling of security practices and its messaging.

A surprising discovery reveals that WordPress potentially tracks user sites by including URLs in API requests. Each request sent to the WordPress.org API contains detailed information, including the version number, website URL, and IP address. This behavior has raised privacy concerns, with users questioning why WordPress needs this data and speculating about its potential use for monitoring hosting changes. The move has sparked debates over privacy policy compliance and whether such practices align with GDPR and community expectations.

The official WordPress account, controlled by Matt Mullenweg, has ramped up its aggressive social media campaign against WP Engine. In a series of tweets, Mullenweg mocked WP Engine's site outages, promoted migration offers, and highlighted user churn statistics to encourage defections. The posts have sparked polarized reactions, with some users condemning the approach as unprofessional, while others see it as part of the ongoing rivalry.

Automattic’s legal team filed an Administrative Motion to Shorten Time, requesting that their Motion to Dismiss be heard concurrently with WP Engine's Motion for Preliminary Injunction. Given their overlapping elements, the motion argues that addressing both issues together promotes efficiency. Observers noted the motion's extended length and questioned its urgency.

Matt Mullenweg’s recent blog post on GPL licensing has sparked criticism within the WordPress community. His push for a stricter interpretation, especially regarding charging for nulled plugins, led many to accuse him of selectively enforcing open-source principles. The post has intensified concerns about WordPress leadership’s stance on GPL freedoms and its effects on the community.

Matt Mullenweg, tweeting from the official WordPress account, responded dismissively to a prominent community member’s critique, leading to backlash across social media. His response, perceived as unprofessional and mocking, sparked reactions from others in the WordPress community, with some expressing frustration over the tone and perceived hostility. Many are now calling for a more respectful approach, using hashtags like #GetMattHelp, as they question the leadership’s professionalism in handling community disagreements.

Automattic and Matt Mullenweg have filed a motion to dismiss several claims in WP Engine's lawsuit, asserting that WP Engine’s allegations lack legal basis. In the filing, Automattic defends its trademark enforcement as a necessary measure to protect the WordPress community. Ironically, the motion criticizes WP Engine for removing WordPress trademarks from its site—exactly what Automattic’s cease-and-desist demanded, a point noted by community members. The motion has sparked further debate about Automattic’s defense strategy, with some finding humor in the document’s language and lengthy sentences.

WordPress, with Matt Mullenweg tweeting directly from the official account, engaged in a heated exchange on social media, targeting users discussing alternative forks of the platform. Mullenweg's comments, criticizing a potential WordPress fork as lacking value and accusing it of misusing funds, were met with strong reactions. Several community members expressed frustration with the tone and language, stating they no longer wished to be associated with WordPress.

Recent policy changes in the WordPress community have raised fears of potential retaliatory actions. Several community members shared incidents where they received direct messages warning of takeovers or control shifts of their plugins if they did not comply with new directives. These reports have led to a growing debate on the perceived risks of retaliation, as developers worry that policy shifts may disproportionately favor certain interests at the expense of others.

WordCamp organizers are now mandated to share social media credentials with Automattic staff, raising suspicions amid an ongoing dispute between WordPress and WP Engine. Organizers express concerns about this move, viewing it as a potential control measure. The directive has led to accusations that the WordPress leadership is stifling positive mentions of WP Engine, adding tension within the WordPress community. Organizers worry that refusal to comply could result in removal from their roles, creating a sense of unease.

Automattic addresses WP Engine’s recent motion, asserting that WP Engine aims to benefit from the WordPress community’s resources without fair contributions. The company stresses the importance of prioritizing the community's efforts and preserving WordPress's integrity. Automattic urges the public to read the full legal filing for a comprehensive understanding, rather than relying on selective interpretations.

The BBC published an article detailing how the WordPress and WP Engine dispute affects businesses worldwide. Highlighting the concerns of small business owners, the report explores the uncertainty and operational disruptions caused by the conflict. The article draws attention to the ripple effects on the broader online economy, emphasizing how changes in key web infrastructure can significantly impact users and businesses. The coverage sheds light on the far-reaching consequences of this ongoing row.

Matt Mullenweg shares in Slack a blog post analyzing Drupal's decline following Acquia's acquisition by private equity investors, which shows sharp market share drops and recent layoffs. While the article warns about private equity's impact on open-source sustainability, community members note the irony, suggesting that both private equity control and centralized leadership can similarly damage open-source communities.

WP Engine outlines recent actions to maintain platform stability amid its ongoing dispute with WordPress. The blog post highlights key events, including legal filings, plugin management updates, and new security measures. WP Engine continues prioritizing service integrity while addressing customer concerns and service disruptions resulting from restricted access to WordPress.org. The company reaffirms its commitment to supporting the WordPress community through these ongoing challenges.

WordPress community members express alarm at Automattic's legal filing, which claims WordPress.org is Matt Mullenweg's personal property rather than belonging to the WordPress Foundation. Developers describe this revelation as a "massive inflection point" in WordPress history, warning it creates a concerning precedent that must be "accounted for." The community expresses surprise and concern at learning the repository isn't owned by Automattic or the WordPress Foundation, with many noting this disclosure fundamentally changes their understanding of WordPress.org's governance. These reactions highlight broader concerns about Mullenweg's claimed personal control over WordPress.org and its implications for the entire WordPress ecosystem.

The U.S. District Court grants WP Engine's motion for a shortened timeline on their preliminary injunction hearing against Automattic and Matt Mullenweg. Judge Araceli Martinez-Olguin sets key dates: Automattic must file their opposition by October 30, WP Engine's reply is due by November 4, and the hearing is scheduled for November 26 in Oakland. This expedited schedule suggests the court recognizes the urgency of WP Engine's requests regarding WordPress.org access and the ACF plugin situation.

Automattic and Matt Mullenweg file an opposition to WP Engine's motion to shorten response time, through their attorneys at Hogan Lovells. They argue the case is fundamentally about WordPress.org - which they claim is owned individually by Mullenweg - rather than WordPress software access. The filing states WP Engine "gambled for the sake of profit" by building their business around Mullenweg's website without any contractual right to access it. Automattic requests the standard two-week response period, citing their parallel work on a motion to dismiss and characterizing WP Engine's request for expedited timing as a "tactical gambit."

Matt Mullenweg publishes a blog post titled "My Freedom of Speech," framing WP Engine's legal actions as an attack on his First Amendment rights. He argues that WordPress.org shouldn't be compelled to distribute WP Engine's code and announces he'll refrain from personally commenting on the case until a judge rules. The community's reaction is overwhelmingly critical, with many pointing out misunderstandings of the First Amendment and freedom of speech. Critics highlight the disconnect between Mullenweg's claims and his actions, including banning users and updating the Code of Conduct to restrict sharing private messages. The response suggests growing frustration with Mullenweg's handling of the situation and concern over his leadership approach.

WordPress.org introduces a new rule to its Code of Conduct, prohibiting the publication of private messages without consent. The change aims to protect private conversations and maintain trust within the community. However, the community's reaction is largely critical, with some viewing it as an attempt by Matt Mullenweg to prevent whistleblowing and protect himself from criticism. Critics point out the apparent contradiction of this rule with allegations that Mullenweg is seeking access to private Slack messages.

DHH tweets his support for WP Engine's preliminary injunction filing against Automattic. He describes the request to return the ACF plugin listing and restore plugin update access as "immensely reasonable." DHH praises the complaint's presentation, calling it well-argued and well-written. He highlights how Automattic's public statements, including interviews, tweets, and blog posts, provide ample evidence for WP Engine's case.

WP Engine files a motion for a preliminary injunction against Automattic and Matt Mullenweg, escalating their ongoing legal battle. The motion alleges extortionate demands from Automattic, retaliation through blocking WordPress.org access, and unauthorized takeover of the ACF plugin. WP Engine reports significant business losses and accuses Automattic of spreading misleading information. The company urges the court to halt Automattic's actions and calls for regulatory involvement, citing potential antitrust violations.

Scott Kingsley Clark, a WordPress contributor, reports his WordPress.org account was unexpectedly disabled without explanation. This action impacts the Pods Framework project, preventing releases due to security measures requiring WordPress.org login. Clark views this as an attack on both himself and the Pods project, potentially linked to the ongoing WP Engine conflict. He has requested to transfer ownership of Pods plugins to ensure continued development.

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.