WP Engine's sanctions motion — accusing Matt Mullenweg of destroying evidence via ephemeral messaging apps — puts the case in front of a federal judge for the first time since the dispute went nuclear.
The clients who have stopped worrying about the Automattic-WP Engine dispute — because nothing visibly broke — and the clients still refreshing court dockets every morning: we think both postures are off. The case is quiet right now, but September 30 is a hard date, and what happens in that courtroom will set the tone for everything that follows in the WordPress ecosystem.
On July 28, 2026, WP Engine filed a motion for sanctions against Matt Mullenweg and Automattic. The allegation is specific: that Mullenweg used disappearing-message settings on Signal, Telegram, and WhatsApp during the period that matters to the litigation, destroying evidence that should have been preserved. Automattic pushed back on August 11, saying it has collected more than 6 terabytes of data and over 1.5 million documents — and that any ephemeral messages Mullenweg sent were personal, not litigation-related. A hearing on that motion is now set for September 30 before Judge Vince Chhabria in the Northern District of California.
That is what is actually at stake on September 30: not a verdict, but a credibility ruling. A sanctions finding against Mullenweg and Automattic would complicate their position in the rest of the case and increase pressure toward settlement or structural changes. A denial keeps things moving on the current track. Either way, the court will have weighed in on the conduct of the party that controls WordPress.org, the plugin repository, the theme directory, and the update infrastructure that millions of production sites depend on.
The party that controls the plugin repository, the theme directory, and the update infrastructure is the one with a sanctions motion filed against it.
For institutions running meaningful public infrastructure on WordPress — the kind that cannot absorb a surprise access change — the September 30 date is a planning signal. A sanctions ruling, positive or negative, will likely accelerate the rest of the case. That is the window to pressure-test contingency posture: know which plugins have no viable alternative, know which ACF version your site is pinned to and whether that version is accessible outside WordPress.org, and know whether your hosting is diversified enough that a policy shift at a single provider does not become your emergency.
We are watching September 30. We will have a plain-language read on what the ruling means — and what, if anything, it changes — within a day of the hearing. If your organization wants a ground-level audit of its WordPress dependencies before that date, the conversation is short and it is free.