David Bridges
WordPress.org has introduced a quirky requirement for users to declare that pineapple is delicious on pizza before gaining access to their accounts. This unusual stipulation is part of an escalating conflict between Matt Mullenweg, co-founder of WordPress, and WP Engine, a prominent web hosting service. This move marks a shift in the ongoing rivalry that has captured the attention of the WordPress community and beyond.
According to reports from 404 Media and further confirmed by Mashable, the login page for WordPress.org now features a mandatory checkbox indicating, “Pineapple is delicious on pizza.” Users are currently unable to log in or create new accounts without checking this box, a change first identified last Sunday. Notably, WordPress.com users are not affected by this new requirement.
Hong Kong Pizza Hut offers free pineapple after Italy objects to Olympic win
The debate surrounding pineapple on pizza has long been a lighthearted yet passionate topic online. However, the context of this specific requirement is far more serious. The introduction of the pineapple pizza checkbox is a direct response to a recent ruling by a California District Court, which granted WP Engine a preliminary injunction prohibiting Automattic from denying the company’s access to WordPress.org.
This injunction also mandated that Automattic remove a previous checkbox on the login page, which required users to assert they were “not affiliated with WP Engine in any way, financially or otherwise.” Users faced access issues unless they ticked that box, leading to frustration and confusion.
Rather than eliminating the checkbox entirely, Automattic appears to have cleverly revised its content, opting instead for the pineapple on pizza statement. This cheeky approach may reflect Mullenweg’s sense of humor in the face of a tense situation.
Credit: Mashable screenshot: WordPress.org
Understanding the Ongoing Conflict Between WordPress and WP Engine
The ongoing conflict between WordPress and WP Engine revolves around serious allegations of trademark infringement. For months, WP Engine and Automattic have been embroiled in a bitter dispute that has ramifications for both companies and the broader WordPress ecosystem.
1. Matt Mullenweg’s Public Critique of WP Engine
The public escalation began on September 21, when Mullenweg criticized WP Engine in a blog post, labeling the company as a “cancer to WordPress.” WP Engine specializes in hosting services tailored for websites built with WordPress’ open-source content management system, which is accessible via WordPress.org. Mullenweg’s remarks have since sparked intense debate, as he accused WP Engine of disabling tracked changes and improperly using branding that infringes on WordPress’ trademarks.
He further emphasized the disparity in contributions to the open-source community, stating, “[WP Engine] generates about half a billion in revenue on top of WordPress yet contributes back only 40 hours a week, whereas Automattic, of similar size, contributes back 3,915 hours weekly.”
2. WP Engine’s Legal Response to Automattic’s Claims
In response to Mullenweg’s public condemnation, WP Engine retaliated with a cease-and-desist letter on September 23, asserting that Automattic was spreading “false factual statements.” The letter also accused Mullenweg of threatening a “scorched earth nuclear approach” towards WP Engine unless they agreed to pay for a license to use WordPress trademarks. Court documents reveal that Automattic allegedly demanded a continuous eight percent of WP Engine’s revenue.
WP Engine contended that such licensing was unnecessary, arguing that their use of WordPress’ trademarks to describe their services fell under fair use. Their letter criticized Mullenweg’s demands as hypocritical, claiming he was masquerading as a protector of the WordPress community while seeking significant financial gain.
Mashable Light Speed
Furthermore, WP Engine asserted that their use of the WordPress marks was consistent with established trademark law and aligned with WordPress’ own guidelines.
3. Automattic’s Counteraction Against WP Engine
In a swift counteraction, Automattic issued its own cease-and-desist letter to WP Engine on the same day, demanding an immediate cessation of all unauthorized use of WordPress and WooCommerce trademarks. Automattic acknowledged its previous outreach to WP Engine regarding trademark licensing but stated that no agreement had been reached. They accused WP Engine of misleading consumers into believing they were associated with WordPress.
The WordPress Foundation’s trademark policy was subsequently updated to specifically address WP Engine, clarifying that while “WP” itself is not trademarked, it should not be utilized in a manner that causes confusion among users.
Mullenweg announced on September 25 that WP Engine had been banned from WordPress.org, leading to significant disruptions for its users. Although the ban was lifted shortly after, it caused considerable operational challenges for WP Engine.
Mullenweg elaborated in a blog post that the rationale behind Automattic’s insistence on compensation was not a mere financial grab but rather an expectation that businesses profiting from an open-source project should contribute back to the community.
4. WP Engine Takes Legal Action Against Automattic
The situation escalated further when WP Engine filed a lawsuit against Automattic and Mullenweg on October 2, citing multiple allegations, including libel, slander, attempted extortion, and unfair competition. In a bid to distance itself from the WordPress brand, WP Engine revised its service names to eliminate any reference to “WordPress” and clarified on its website that it is “not endorsed or owned by, or affiliated with” the WordPress Foundation or WooCommerce.
A WP Engine spokesperson commented on the situation, stating, “Automattic’s claim that WP Engine needs a license to use the WordPress name is fundamentally incorrect and demonstrates a lack of understanding of trademark law.” They also mentioned that the company has already taken steps to address Automattic’s concerns by removing certain references from their marketing materials.
In light of these ongoing legal disputes, Automattic maintains that WP Engine’s access to WordPress code and plugins has never been restricted.
Automattic strongly asserts that WP Engine is seeking to compel them to allow free hosting and distribution of plugins on WordPress.org without any obligations, which they view as unreasonable.
The Curious Connection Between Pineapple Pizza and the WordPress Lawsuit
This brings us back to the peculiar pineapple pizza checkbox on WordPress.org. In early October, Mullenweg altered the login page to include a checkbox mandating that users declare no affiliation with WP Engine. He mentioned in a Slack post that this was part of the ongoing measures against WP Engine.
However, following the court’s injunction last Tuesday, that checkbox has now transformed into one that demands users express their allegiance to the pineapple pizza debate. The rationale behind this seemingly whimsical requirement remains ambiguous, leaving many to wonder about its relevance to the ongoing legal issues.
While Automattic has not publicly addressed the change, Mullenweg’s brief mention on X suggests it might be a lighthearted jab amidst serious circumstances. Even if the company is dealing with significant challenges, it seems unlikely that Automattic would genuinely seek users’ opinions on pizza toppings.
var facebookPixelLoaded = false;
window.addEventListener(‘load’, function(){
document.addEventListener(‘scroll’, facebookPixelScript);
document.addEventListener(‘mousemove’, facebookPixelScript);
})
function facebookPixelScript() {
if (!facebookPixelLoaded) {
facebookPixelLoaded = true;
document.removeEventListener(‘scroll’, facebookPixelScript);
document.removeEventListener(‘mousemove’, facebookPixelScript);
!function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;
n.push=n;n.loaded=!0;n.version=’2.0′;n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window,
document,’script’,’//connect.facebook.net/en_US/fbevents.js’);
fbq(‘init’, ‘1453039084979896’);
fbq(‘track’, “PageView”);
}
}
Daniel Mercer
Brandon Fletcher
