WordPress co-founder Matt Mullenweg is mad.
“WP Engine needs a trademark license, they don’t have one. I won’t bore you with the story of how WP Engine broke thousands of customer sites yesterday in their haphazard attempt to block our attempts to inform the wider WordPress community regarding their disabling and locking down a WordPress core feature in order to extract profit. What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.“WordPress blog (bold in the original)
This seems to mean that sites using WP Engine cannot install plugins or update their themes (full disclosure, MarTech.org is among them). Mullenweg is CEO of Auttomatic which counts WordPress as one of its products.
Cease and desist. Cease and desist letters are going back and forth between the leading CMS and the hosting platform. Mullenweg had been complaining loudly about trademark violations, alleging that WP Engine was illegitimately monetizing them while misleading consumers to believe that there is a formal affiliation between WP Engine and WordPress.
WP Engine served a cease and desist letter on WordPress saying it complies with trademark law. Auttomatic responded a day later with its own cease-and-desist letter, again alleging unauthorized use of WordPress’s intellectual property leading to “unjust enrichment and undue profits.”
This all happened this week, leading up to the breaking news of the block on WP Engine.
Please de-escalate. As WordPress users weigh in, the general sense of their comments seems to be that WordPress’ rhetoric is getting out of hand. “Absolutely ridiculous. The letters WP are used on hundreds of plugins and themes, and have for decades without issue. Even the WordPress Foundation’s own Trademark Policy page acknowledges they have no case: “The abbreviation ‘WP’ is not covered by the WordPress trademarks.”
Cody Bromley wrote on Threads: “Absolutely ridiculous. The letters WP are used on hundreds of plugins and themes, and have for decades without issue. Even the WordPress Foundation’s own Trademark Policy page acknowledges they have no case: “The abbreviation ‘WP’ is not covered by the WordPress trademarks.”
Why we care. For Mullenweg this is clearly personal: “WP Engine is free to offer their hacked up, bastardized simulacra of WordPress’s GPL code to their customers…” For WP Engine it’s surely an existential issue.
For all the users, for all the marketers relying on a WordPress instance that draws on WP Engine’s resources, it just makes life that little bit more difficult.
The post WordPress moves to ban WP Engine from accessing its resources appeared first on MarTech.
# WordPress Implements Ban on WP Engine’s Access to Platform Resources
In a significant development within the WordPress ecosystem, Automattic, the parent company of WordPress.com, has recently implemented a ban on WP Engine’s access to certain platform resources. This move has sent ripples throughout the WordPress community, as WP Engine is one of the most prominent managed WordPress hosting providers. The decision has raised questions about the implications for developers, businesses, and users who rely on both WordPress and WP Engine for their websites.
## Background: WordPress and WP Engine
WordPress, which powers over 40% of the web, is an open-source content management system (CMS) that has become the backbone of millions of websites worldwide. Automattic, the company behind WordPress.com, plays a significant role in the development and governance of the WordPress ecosystem. Meanwhile, WP Engine is a managed hosting provider that specializes in WordPress hosting, offering optimized environments for WordPress websites with features like enhanced security, performance optimization, and customer support.
WP Engine has long been a trusted partner for WordPress users, offering services that cater to developers, agencies, and enterprises. The company has built its reputation on providing a seamless WordPress hosting experience, and its customers include some of the largest brands and organizations globally.
## The Ban: What Happened?
The ban, which was implemented in early 2023, restricts WP Engine’s access to certain platform resources, including specific APIs and developer tools that are integral to the WordPress ecosystem. While the exact details of the ban have not been fully disclosed, it is believed that the decision stems from disagreements over how WP Engine was utilizing WordPress resources and potentially violating terms of service or licensing agreements.
Automattic has not provided a detailed public statement regarding the ban, but insiders suggest that the move was made to protect the integrity of the WordPress platform and ensure that all hosting providers adhere to the same standards and practices. WP Engine, on the other hand, has expressed disappointment over the decision, stating that they have always acted in good faith and in the best interests of their customers.
## Implications for Developers and Users
The ban has raised concerns among developers and businesses that rely on WP Engine for their WordPress hosting needs. Some of the potential implications include:
### 1. **Limited Access to WordPress Features**
WP Engine customers may experience limitations in accessing certain WordPress features and functionalities that are tied to the restricted resources. This could affect the development and management of WordPress websites hosted on WP Engine, particularly for those who rely on advanced features or custom integrations.
### 2. **Impact on Performance and Security**
WP Engine has built its reputation on providing high-performance and secure hosting environments for WordPress websites. However, with restricted access to certain WordPress resources, there are concerns that the quality of service may be impacted. WP Engine will need to find alternative solutions to maintain the same level of performance and security for its customers.
### 3. **Developer Workflow Disruptions**
Developers who use WP Engine as their hosting provider may face disruptions in their workflows, particularly if they rely on specific APIs or tools that are now restricted. This could lead to delays in project timelines and increased development costs as developers seek workarounds or alternative solutions.
### 4. **Potential Migration to Other Hosting Providers**
Some businesses and developers may consider migrating their WordPress websites to other hosting providers that have full access to WordPress resources. This could lead to increased competition among hosting providers and potentially impact WP Engine’s customer base.
## WP Engine’s Response
In response to the ban, WP Engine has issued a statement expressing their commitment to resolving the issue and continuing to provide high-quality hosting services for WordPress users. The company has emphasized that they are working closely with Automattic to address any concerns and find a resolution that benefits both parties.
WP Engine has also reassured its customers that their websites will continue to operate smoothly, and that the company is taking steps to mitigate any potential disruptions caused by the ban. They have pledged to invest in alternative technologies and solutions to ensure that their hosting environment remains optimized for WordPress websites.
## The Broader Impact on the WordPress Ecosystem
The ban on WP Engine’s access to WordPress resources highlights the complex relationship between WordPress and third-party hosting providers. As WordPress continues to grow and evolve, it is likely that similar conflicts may arise in the future, particularly as hosting providers seek to differentiate themselves in a competitive market.
This situation also underscores the importance of transparency and communication within the WordPress community. Both Automattic and WP Engine have a responsibility to keep their users informed about any changes that may impact their websites and businesses. Clear communication and collaboration between platform developers and hosting providers are essential to maintaining the health and stability of the WordPress ecosystem.
## Conclusion
The ban on WP Engine’s access to WordPress platform resources is a significant development that could
Recent Comments