**WordPress.org Now Requires Users to Confirm Pineapple Pizza Preference Amid Legal Battle with WP Engine**

In an unexpected turn, WordPress.org has implemented a new login stipulation: users are now required to state that “pineapple is delicious on pizza” prior to accessing their accounts. This playful move marks the latest twist in a growing legal and public relations conflict between WordPress co-founder and Automattic CEO Matt Mullenweg and web hosting provider WP Engine.

### Pineapple Pizza Checkbox Triggers Debate

As initially reported by *404 Media* and verified by *Mashable*, the login interface of WordPress.org now includes a checkbox alongside the phrase “Pineapple is delicious on pizza.” Users are unable to log in or establish new accounts without checking this box, a modification that came to light on Sunday. Importantly, this change does not pertain to WordPress.com, which functions independently.

The discussion surrounding pineapple as a pizza topping has long been a lighthearted subject online, but its introduction in this context appears to have a more serious, contentious flavor. This new requirement comes on the heels of a ruling from a California District Court last Tuesday, which granted WP Engine a preliminary injunction against Automattic. The court mandated Automattic to eliminate an earlier checkbox requiring users to declare they had “no affiliation with WP Engine in any way, financially or otherwise.” Rather than scrapping the checkbox entirely, Automattic opted to substitute it with the pineapple pizza confirmation.

### The WordPress vs. WP Engine Timeline of Dispute

The persistent contention between Automattic and WP Engine revolves around claimed trademark violations and broader conflicts regarding contributions to the WordPress ecosystem. Here’s how the situation has unfolded:

#### 1. **Mullenweg Attacks WP Engine**
The public conflict flared on September 21, when Mullenweg penned a blog post denouncing WP Engine as a “cancer to WordPress.” WP Engine, a third-party hosting entity for WordPress sites, was accused of obstructing tracked changes, breaching WordPress trademarks, and making only minimal contributions to the open-source project. Mullenweg asserted that while WP Engine generates approximately half a billion dollars in revenue each year, it only contributes about 40 hours per week to WordPress development compared to Automattic’s 3,915 hours.

#### 2. **WP Engine Issues a Cease-and-Desist Notice**
On September 23, WP Engine retaliated with a cease-and-desist letter, alleging Mullenweg had disseminated inaccurate statements and warned of a “scorched earth nuclear approach” unless WP Engine compensated Automattic for the right to use WordPress trademarks. Automattic was reportedly asking for 8% of WP Engine’s revenue as a licensing charge. WP Engine contended that its use of WordPress trademarks fell under fair use and accused Mullenweg of exploiting his position for financial advantage.

#### 3. **Automattic Strikes Back and Bans WP Engine**
Automattic released its own cease-and-desist letter on the same day, insisting WP Engine halt its use of WordPress and WooCommerce trademarks without permission. The WordPress Foundation also revised its trademark policy to discourage the usage of “WP” in ways that could mislead users into believing WP Engine has official ties to WordPress.

On September 25, Mullenweg revealed that WP Engine had been blocked from WordPress.org, disrupting numerous sites and hindering updates. Although the ban was briefly lifted two days later, it resulted in serious operational hurdles for WP Engine.

#### 4. **WP Engine Initiates Legal Action**
The situation intensified on October 2, when WP Engine filed a lawsuit against Automattic and Mullenweg, claiming libel, slander, attempted extortion, and unfair competition. WP Engine also excluded the term “WordPress” from its service plans and clarified on its website that it does not have any affiliations with the WordPress Foundation or WooCommerce.

In response, Automattic refuted WP Engine’s allegations, asserting that the company had never lost access to WordPress code or plugins. Automattic claimed WP Engine was seeking to compel Automattic to host and distribute its plugins on WordPress.org for free, despite having no obligation to do so.

### Pineapple Pizza Checkbox: A Gag or an Indicator?

The addition of the pineapple pizza checkbox seems to be a humorous retort to the court’s injunction. In early October, Mullenweg had implemented a checkbox requiring users to assert no association with WP Engine as part of the prohibition. After the court mandated its removal, the checkbox was substituted with the pineapple pizza affirmation.

While the link between pineapple pizza and the ongoing legal dispute is uncertain, the maneuver appears to serve as a lighthearted dig amid serious legal proceedings. Automattic has not addressed the alteration, and Mullenweg has merely shared a post on X (formerly Twitter) drawing attention to the update.

Whether this serves as a whimsical diversion or a nuanced commentary on the broader dispute, one thing remains clear: the WordPress-WP Engine conflict is far from over.