{"id":7831,"date":"2024-11-19T13:34:46","date_gmt":"2024-11-19T12:34:46","guid":{"rendered":"https:\/\/weblounge.reimagine.link\/?p=7831"},"modified":"2024-11-19T13:48:27","modified_gmt":"2024-11-19T12:48:27","slug":"wordpress-vs-wp-engine-my-open-letter-to-matt-mullenweg-and-the-wordpress-community","status":"publish","type":"post","link":"https:\/\/weblounge.reimagine.link\/en\/wordpress-vs-wp-engine-my-open-letter-to-matt-mullenweg-and-the-wordpress-community\/","title":{"rendered":"WordPress vs. WP Engine: My Open Letter to Matt Mullenweg and the WordPress Community"},"content":{"rendered":"<div class=\"wpb-content-wrapper\"><section class=\"l-section wpb_row height_medium\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row type_default valign_top\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"w-post-elm post_image stretched\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"585\" src=\"data:image\/svg+xml,%3Csvg xmlns=%22http:\/\/www.w3.org\/2000\/svg%22 viewBox=%220 0 1024 585%22%3E%3C\/svg%3E\" data-lazy-type=\"image\" data-src=\"https:\/\/weblounge.reimagine.link\/wp-content\/uploads\/2024\/11\/8d99f772-7b71-4390-985d-54351449d0cc-1024x585.webp\" class=\"lazy lazy-hidden attachment-large size-large wp-post-image\" alt=\"WordPress vs. WP Engine: My Open Letter to Matt Mullenweg and the WordPress Community\" srcset=\"\" data-srcset=\"https:\/\/weblounge.reimagine.link\/wp-content\/uploads\/2024\/11\/8d99f772-7b71-4390-985d-54351449d0cc-1024x585.webp 1024w, https:\/\/weblounge.reimagine.link\/wp-content\/uploads\/2024\/11\/8d99f772-7b71-4390-985d-54351449d0cc-300x171.webp 300w, https:\/\/weblounge.reimagine.link\/wp-content\/uploads\/2024\/11\/8d99f772-7b71-4390-985d-54351449d0cc.webp 1792w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" title=\"Chicago - Paris - Berlin - Munich - Frankfurt - W\u00fcrzburg - Germany - Europe Webdesign\"><\/div><h2 class=\"w-post-elm post_title entry-title\" itemprop=\"headline\">WordPress vs. WP Engine: My Open Letter to Matt Mullenweg and the WordPress Community<\/h2><div class=\"wpb_text_column\" ><div class=\"wpb_wrapper\"><h1><span data-preserver-spaces=\"true\">The feud between <a href=\"https:\/\/www.theregister.com\/2024\/11\/15\/wp_engine_antitrust_automattic_lawsuit\/\" target=\"_blank\" rel=\"noopener\">Automattic<\/a> (WordPress) and <a href=\"https:\/\/observer.com\/2024\/11\/wordpress-founder-matt-mullenweg-energized-amid-wp-engine-battle\/\" target=\"_blank\" rel=\"noopener\">WP Engine <\/a><\/span><\/h1>\n<p><span data-preserver-spaces=\"true\">has <a href=\"https:\/\/techcrunch.com\/2024\/11\/07\/wordpress-vs-wp-engine-drama-explained\/\" target=\"_blank\" rel=\"noopener\">sparked intense discussion<\/a> about the practices of WordPress hosting providers, plugin developers, and theme creators. As a long-time <\/span><a class=\"editor-rtfLink\" href=\"https:\/\/weblounge.reimagine.link\/en\/\" target=\"_blank\" rel=\"noopener\"><span data-preserver-spaces=\"true\">WordPress developer<\/span><\/a><span data-preserver-spaces=\"true\"> with over 21 years of experience, I\u2019ve seen firsthand the challenges users face and the urgent need for improved oversight in the <a href=\"https:\/\/www.bbc.com\/news\/articles\/cm2y7eyp3zpo\" target=\"_blank\" rel=\"noopener\">WordPress ecosystem<\/a>.<\/span><\/p>\n<h3><span data-preserver-spaces=\"true\">Hosting Issues: A Developer\u2019s Perspective<\/span><\/h3>\n<p><span data-preserver-spaces=\"true\">Hosting companies often wield significant power, sometimes to the detriment of their customers. I\u2019ve personally faced such issues with DreamHost (despite its presence and influence within the WordPress community\u2014partly due <\/span><span data-preserver-spaces=\"true\">their<\/span><span data-preserver-spaces=\"true\"> leaders being actively involved in the WordPress forums i.e. Mika Epstein and <\/span><strong><a class=\"editor-rtfLink\" href=\"https:\/\/www.linkedin.com\/comm\/in\/dreamhostmichael?midToken=AQG8pFpE9eV-6Q&amp;midSig=28xjoRdehDvFw1&amp;trk=eml-email_accept_invite_single_01-hero-3-prof%7Ename&amp;trkEmail=eml-email_accept_invite_single_01-hero-3-prof%7Ename-null-e58zsh%7Ekhwnfau9%7E51-null-neptune%2Fprofile%7Evanity%2Eview&amp;lipi=urn%3Ali%3Apage%3Aemail_email_accept_invite_single_01%3BSJp1TFRcSn2EM%2BJvCauz7Q%3D%3D\" target=\"_blank\" rel=\"noopener\"><span data-preserver-spaces=\"true\">Michael Rodriguez<\/span><\/a><\/strong><span data-preserver-spaces=\"true\">\u2014<\/span><strong><u><span data-preserver-spaces=\"true\">is not a hosting provider I would recommend<\/span><\/u><\/strong><span data-preserver-spaces=\"true\">), 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:<\/span><\/p>\n<ul>\n<li><span data-preserver-spaces=\"true\">Keep domains separate from hosting providers.<\/span><\/li>\n<li><span data-preserver-spaces=\"true\">Automate <a href=\"https:\/\/weblounge.reimagine.link\/en\/eu-web-design-germany-spain-google-ai-and-seo\/\">cloud<\/a> backups.<\/span><\/li>\n<li><span data-preserver-spaces=\"true\">Optimize PHP and reduce unnecessary plugins.<\/span><\/li>\n<\/ul>\n<p><span data-preserver-spaces=\"true\">WP Engine is another hosting provider under fire, accused by <a href=\"https:\/\/slate.com\/technology\/2024\/10\/wordpress-wpengine-matt-mullenweg-drama-explained.html\" target=\"_blank\" rel=\"noopener\">Matt Mullenweg<\/a> of failing to contribute to the <a href=\"https:\/\/weblounge.reimagine.link\/en\/services\/web-design-wuerzburg\/wuerzburg-web-design-wordpress-development\/\">WordPress <\/a>ecosystem and misusing the WordPress trademark to confuse customers. Mullenweg\u2019s criticism highlights WP Engine\u2019s deviation from community norms:<\/span><\/p>\n<p><span data-preserver-spaces=\"true\">&#8220;There has never been anything like this. WP Engine\u2019s abuse of our trademarks is egregious.&#8221;<\/span><\/p>\n<p><span data-preserver-spaces=\"true\"><a href=\"https:\/\/www.theverge.com\/2024\/10\/31\/24284537\/wordpress-court-dismiss-wp-engine-lawsuit\" target=\"_blank\" rel=\"noopener\">WP Engine<\/a>\u2019s proprietary forks and lack of contributions to WordPress have alienated <\/span><span data-preserver-spaces=\"true\">both<\/span><span data-preserver-spaces=\"true\"> developers and end users. If WP Engine respected its customers, it would drop its lawsuit and dedicate revenue to WordPress development.<\/span><\/p>\n<h3><span data-preserver-spaces=\"true\">Plugin Vulnerabilities: A Developer\u2019s Nightmare<\/span><\/h3>\n<p><span data-preserver-spaces=\"true\"><a href=\"https:\/\/weblounge.reimagine.link\/en\/the-5-reasons-why-your-website-is-unwelcoming\/\">My experience<\/a> with StellarWP\u2019s iThemes plugin <\/span><em><span data-preserver-spaces=\"true\">Restrict Content<\/span><\/em><span data-preserver-spaces=\"true\"> 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.<\/span><\/p>\n<p><span data-preserver-spaces=\"true\">Despite verified reports from Securi and Stripe, StellarWP <\/span><span data-preserver-spaces=\"true\">support<\/span> <span data-preserver-spaces=\"true\">tearm<\/span><\/p>\n<p><strong><span data-preserver-spaces=\"true\">Rebecca Diamond <\/span><\/strong><span data-preserver-spaces=\"true\">denied the issues and banned users who raised concerns on WordPress forums. Thanks to one of the customers&#8217; hosting which is superior <\/span><a class=\"editor-rtfLink\" href=\"http:\/\/inmotion.host\/3c27eff5\" target=\"_blank\" rel=\"noopener\"><span data-preserver-spaces=\"true\">InMotion Hosting<\/span><\/a><span data-preserver-spaces=\"true\">&#8216;s technical support also helped identify the vulnerability. It\u2019s clear that:<\/span><\/p>\n<ul>\n<li><span data-preserver-spaces=\"true\">Plugin vulnerabilities must be addressed promptly.<\/span><\/li>\n<li><span data-preserver-spaces=\"true\">Support teams should assist, not alienate, affected users.<\/span><\/li>\n<\/ul>\n<h3><span data-preserver-spaces=\"true\">The Bigger Picture: Themes and Plugins<\/span><\/h3>\n<p><span data-preserver-spaces=\"true\">Themes and plugins are essential to WordPress\u2019s 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 o<\/span><span data-preserver-spaces=\"true\">n:<\/span><\/p>\n<ul>\n<li><span data-preserver-spaces=\"true\">Timely security updates and bug fixes.<\/span><\/li>\n<li><span data-preserver-spaces=\"true\">Transparent support response times.<\/span><\/li>\n<li><span data-preserver-spaces=\"true\">Fair practices for free vs. paid versions.<\/span><\/li>\n<\/ul>\n<h3><span data-preserver-spaces=\"true\">Moving Forward: Oversight and Accountability<\/span><\/h3>\n<p><span data-preserver-spaces=\"true\">WordPress thrives because it\u2019s free, accessible, and supported by a vibrant community. To protect this legacy, the following changes are essential:<\/span><\/p>\n<ul>\n<li><span data-preserver-spaces=\"true\">Hosting providers should license the WordPress trademark or contribute to its development.<\/span><\/li>\n<li><span data-preserver-spaces=\"true\">Plugin and theme developers need stricter oversight, including mandatory support for vulnerabilities and fair pricing models.<\/span><\/li>\n<li><span data-preserver-spaces=\"true\">WordPress forums should ensure open dialogue; banning users for raising legitimate concerns undermines the community.<\/span><\/li>\n<\/ul>\n<h3><span data-preserver-spaces=\"true\">Final Thoughts<\/span><\/h3>\n<p><span data-preserver-spaces=\"true\">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.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span data-preserver-spaces=\"true\">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.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><em><span data-preserver-spaces=\"true\">Disclaimer: I am not affiliated with Matt Mullenweg, Automattic, or WordPress. My experiences and opinions are shared to foster constructive dialogue.<\/span><\/em><\/p>\n<p>&nbsp;<\/p>\n<p><span data-preserver-spaces=\"true\">Let\u2019s make WordPress better\u2014together.<\/span><\/p>\n<p><span data-preserver-spaces=\"true\">Sincerely Robert<\/span><\/p>\n<p>#WordPress, #OpenLetter, #WPEngine, #WebDevelopment, #TechEthics, #MattMullenweg<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>My open letter to Matt Mullenweg and the WordPress community: Addressing the WP Engine feud, plugin vulnerabilities, and the need for stronger accountability. Let\u2019s make WordPress better, together!<\/p>\n","protected":false},"author":1,"featured_media":7832,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25,33],"tags":[128,131,130,26,129],"class_list":["post-7831","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-webdesigner","category-wordpress-3","tag-openletter","tag-techethics","tag-webdevelopment","tag-wordpress","tag-wpengine"],"_links":{"self":[{"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/posts\/7831","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/comments?post=7831"}],"version-history":[{"count":7,"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/posts\/7831\/revisions"}],"predecessor-version":[{"id":7840,"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/posts\/7831\/revisions\/7840"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/media\/7832"}],"wp:attachment":[{"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/media?parent=7831"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/categories?post=7831"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/weblounge.reimagine.link\/en\/wp-json\/wp\/v2\/tags?post=7831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}