The feud between Automattic (WordPress) and WP Engine
has sparked intense discussion about the practices of WordPress hosting providers, plugin developers, and theme creators. As a long-time WordPress developer with over 21 years of experience, I’ve seen firsthand the challenges users face and the urgent need for improved oversight in the WordPress ecosystem.
Hosting Issues: A Developer’s Perspective
Hosting companies often wield significant power, sometimes to the detriment of their customers. I’ve personally faced such issues with DreamHost (despite its presence and influence within the WordPress community—partly due their leaders being actively involved in the WordPress forums i.e. Mika Epstein and Michael Rodriguez—is not a hosting provider I would recommend), where growing traffic on my 20+ client websites led to shutdown threats for violating shared hosting policies. Instead of cooperating, I had to scramble to back up data and fight to regain access to domains, ultimately resorting to legal threats. This experience taught me critical lessons:
- Keep domains separate from hosting providers.
- Automate cloud backups.
- Optimize PHP and reduce unnecessary plugins.
WP Engine is another hosting provider under fire, accused by Matt Mullenweg of failing to contribute to the WordPress ecosystem and misusing the WordPress trademark to confuse customers. Mullenweg’s criticism highlights WP Engine’s deviation from community norms:
“There has never been anything like this. WP Engine’s abuse of our trademarks is egregious.”
WP Engine’s proprietary forks and lack of contributions to WordPress have alienated both developers and end users. If WP Engine respected its customers, it would drop its lawsuit and dedicate revenue to WordPress development.
Plugin Vulnerabilities: A Developer’s Nightmare
My experience with StellarWP’s iThemes plugin Restrict Content highlights the dangers of poorly maintained plugins. A security flaw in their default membership level (ID = 0) allowed hackers to exploit Stripe payment processing, generating thousands of fraudulent transactions per hour. This led to hosting terminations and hefty fraud fees for my clients.
Despite verified reports from Securi and Stripe, StellarWP support tearm
Rebecca Diamond denied the issues and banned users who raised concerns on WordPress forums. Thanks to one of the customers’ hosting which is superior InMotion Hosting‘s technical support also helped identify the vulnerability. It’s clear that:
- Plugin vulnerabilities must be addressed promptly.
- Support teams should assist, not alienate, affected users.
The Bigger Picture: Themes and Plugins
Themes and plugins are essential to WordPress’s versatility, but many paid options fail to deliver value. Developers often prioritize monetization over functionality, pushing pro versions for basic features. WordPress must enforce stricter oversight on:
- Timely security updates and bug fixes.
- Transparent support response times.
- Fair practices for free vs. paid versions.
Moving Forward: Oversight and Accountability
WordPress thrives because it’s free, accessible, and supported by a vibrant community. To protect this legacy, the following changes are essential:
- Hosting providers should license the WordPress trademark or contribute to its development.
- Plugin and theme developers need stricter oversight, including mandatory support for vulnerabilities and fair pricing models.
- WordPress forums should ensure open dialogue; banning users for raising legitimate concerns undermines the community.
Final Thoughts
WordPress has grown immensely over its 21-year history, but now is the time for greater accountability. Matt Mullenweg and the WordPress community must address these issues to ensure the platform remains a beacon of innovation and accessibility.
This open letter is a call for collaboration and action. I hope it reaches WP Engine, Matt Mullenweg, and others who shape the WordPress ecosystem.
Disclaimer: I am not affiliated with Matt Mullenweg, Automattic, or WordPress. My experiences and opinions are shared to foster constructive dialogue.
Let’s make WordPress better—together.
Sincerely Robert
#WordPress, #OpenLetter, #WPEngine, #WebDevelopment, #TechEthics, #MattMullenweg
