{"id":5223,"date":"2024-10-14T14:56:24","date_gmt":"2024-10-14T21:56:24","guid":{"rendered":"https:\/\/www.ultimatewb.com\/blog\/?p=5223"},"modified":"2024-10-14T14:58:26","modified_gmt":"2024-10-14T21:58:26","slug":"wordpress-org-faces-turmoil-over-acf-plugin-controversy-a-battle-for-control","status":"publish","type":"post","link":"https:\/\/www.ultimatewb.com\/blog\/5223\/wordpress-org-faces-turmoil-over-acf-plugin-controversy-a-battle-for-control\/","title":{"rendered":"WordPress.org Faces Turmoil Over ACF Plugin Controversy: A Battle for Control"},"content":{"rendered":"\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress.jpeg\">    <picture>\n                <source type=\"image\/webp\" srcset=\"https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-91x150.webp 91w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-302x500.webp 302w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-483x800.webp 483w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-610x1010.webp 610w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-724x1200.webp 724w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress.webp 1170w\" sizes=\"(max-width: 767px) 100vw, 1170px\">\n                <img src=\"https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress.jpeg\" \n             srcset=\"https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-91x150.jpeg 91w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-302x500.jpeg 302w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-483x800.jpeg 483w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-610x1010.jpeg 610w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-724x1200.jpeg 724w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-768x1272.jpeg 768w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress-927x1536.jpeg 927w, https:\/\/www.ultimatewb.com\/blog\/wp-content\/uploads\/acf-security-incident-wordpress.jpeg 1170w\" \n             sizes=\"(max-width: 767px) 100vw, 1170px\" \n             width=\"1170\" \n             height=\"1938\" \n             alt=\"acf-security-incident-wordpress\" \n             loading=\"lazy\" \n              \n             decoding=\"async\" \n             class=\"wp-image-5224\" >\n    <\/picture>\n    <\/a><\/figure>\n\n\n\n<p>The <a href=\"https:\/\/www.ultimatewb.com\/blog\/?s=wordpress\">WordPress<\/a> community is in an uproar following a controversial move by <a href=\"https:\/\/www.ultimatewb.com\/blog\/?s=Matt+Mullenweg\">Matt Mullenweg<\/a>, CEO of Automattic (owner of WordPress.com) and a key figure behind WordPress.org. On October 12th, Mullenweg took an unprecedented step by forcibly replacing the popular Advanced Custom Fields (ACF) plugin and its listing on WordPress.org with a new &#8220;Secure Custom Fields&#8221; plugin. This action has sparked concerns about stability, trust, and the future of WordPress.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The ACF Controversy: What Happened?<\/strong><\/h2>\n\n\n\n<p>The Advanced Custom Fields plugin, developed by the team at <a href=\"https:\/\/www.ultimatewb.com\/blog\/5192\/the-war-on-wordpress-wp-engine-vs-matt-mullenweg-heats-up-september-2024-update\/\">WP Engine<\/a>, has been a staple in the WordPress ecosystem for over a decade. It allows users to easily create custom fields for posts, pages, and other content types. However, on October 12th, the official ACF plugin on WordPress.org was replaced with a new plugin called &#8220;Secure Custom Fields.&#8221; This new plugin, developed by Automattic, raised concerns within the community.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Concerns and Risks:<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Unstable Code:<\/strong> The &#8220;Secure Custom Fields&#8221; plugin is untested and unapproved by the original ACF development team. This raises questions about its stability and potential compatibility issues with existing websites using ACF.<\/li>\n\n\n\n<li><strong>Loss of Trust:<\/strong> The forceful takeover of the ACF plugin and listing has shaken user confidence in the WordPress.org repository. Users worry about the future of other plugins and the potential for similar interventions.<\/li>\n\n\n\n<li><strong>Fragmentation:<\/strong> This move could lead to a situation where users have to choose between the original ACF plugin and the Automattic version, potentially creating confusion and compatibility issues.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Users Can Do:<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed Hosting Users:<\/strong> Users on platforms like WP Engine and Flywheel who are already using the paid version of ACF are not affected.<\/li>\n\n\n\n<li><strong>Free ACF Users (Non-Managed Hosting):<\/strong> Download the genuine version 6.3.8 of ACF directly from advancedcustomfields.com to avoid updates with the unapproved code.<\/li>\n\n\n\n<li><strong>Users with &#8220;Secure Custom Fields&#8221;:<\/strong> Follow the process above to switch back to the genuine ACF version.<\/li>\n<\/ul>\n\n\n\n<p>If you&#8217;re just using WordPress for the blog section of your website built with <a href=\"https:\/\/www.ultimatewb.com\">UltimateWB<\/a>, chances are you haven&#8217;t been using the ACF plugin, so no issues there. Actually, you could cut out all the controversies and instability of WordPress from affecting your website and opt to use the UltimateWB built-in Articles app instead.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Future of WordPress.org:<\/strong><\/h2>\n\n\n\n<p>This controversy raises questions about the future of WordPress.org. The <a href=\"https:\/\/www.ultimatewb.com\/blog\/?s=open+source\">open-source<\/a> nature of the platform has been thought by many as a point of strength, but this incident highlights the potential for control struggles and conflicts. It remains to be seen how Automattic will address these concerns and rebuild trust with the community.<\/p>\n\n\n\n<p><strong>Additional Resources:<\/strong><\/p>\n\n\n\n<p>WP Engine Security Team Email: <\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Hi xxx,<\/p>\n\n\n\n<p>We are reaching out promptly and directly to inform you of Matt Mullenweg\u2019s (CEO of Automattic and owner of WordPress.org) unprecedented and appalling actions on Oct 12th to forcibly appropriate the Advanced Custom Fields (ACF) plugin and .org listing. The potential impact of Mr. Mullenweg\u2019s improper action is that millions of existing installations of ACF will be updated with code that is unapproved and untrusted by the experts on the ACF team at WP Engine. We want to highlight how you can immediately reduce your exposure and risk now, and ensure you are using the genuine ACF. If your website is hosted on WP Engine or Flywheel or you are an ACF PRO customer \u2013 you are not impacted and do not need to take any action. You will continue to get the latest updates, securely from the experts on the ACF team.<\/p>\n\n\n\n<p>If you have a website that is NOT managed on WP Engine or Flywheel AND are using the free version of ACF you must perform a one-time download of the 6.3.8 version via advancedcustomfields.com in order to get genuine ACF updates and remain safe in the future. After this one-time download you will be able to safely update as usual via the WP Admin panel.<\/p>\n\n\n\n<p>If your site has already updated to the modified \u201cSecure Custom Fields\u201d plugin, you can also follow the process above to get back to a genuine version of ACF, and should not experience any loss of configuration or data doing so before there is further change to the ACF code.<\/p>\n\n\n\n<p>The WordPress community has trusted ACF for over a decade and the expert stewards of ACF will continue to support and enhance the capabilities that our users love and trust. If you have any questions our technical support team is standing by to support you. On behalf of our entire team, we are grateful for the continued opportunity to serve your customers, your business and team.<\/p>\n\n\n\n<p>For a more in-depth overview of what has happened with the free ACF plugin and WordPress.org, you can read this post here.<\/p>\n\n\n\n<p>The WP Engine Security team<\/p>\n<\/blockquote>\n\n\n\n<p>Advanced Custom Fields Website: <a href=\"https:\/\/www.advancedcustomfields.com\/resources\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/www.advancedcustomfields.com\/resources\/<\/a><\/p>\n\n\n\n<p>Are you ready to design &amp; build your own website? Learn more about&nbsp;<a href=\"https:\/\/www.ultimatewb.com\/\">UltimateWB<\/a>! We also offer&nbsp;<a href=\"https:\/\/www.ultimatewb.com\/web-design-packages\">web design packages<\/a>&nbsp;if you would like your website designed and built for you.<\/p>\n\n\n\n<p><em>Got a techy\/website question? Whether it\u2019s about UltimateWB or another website builder, web hosting, or other aspects of websites, just send in your question in the&nbsp;<a href=\"https:\/\/www.ultimatewb.com\/ask-david\">\u201cAsk David!\u201d form<\/a>. We will email you when the answer is posted on the UltimateWB \u201cAsk David!\u201d section.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The WordPress community is in an uproar following a controversial move by Matt Mullenweg, CEO of Automattic (owner of WordPress.com) and a key figure behind WordPress.org. On October 12th, Mullenweg took an unprecedented step by forcibly replacing the popular Advanced &hellip; <a href=\"https:\/\/www.ultimatewb.com\/blog\/5223\/wordpress-org-faces-turmoil-over-acf-plugin-controversy-a-battle-for-control\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[621],"tags":[3294,3297,2932,2935,3299,3298,3254,2933,2934,3295,3257,3253],"class_list":["post-5223","post","type-post","status-publish","format-standard","hentry","category-technology-in-the-news","tag-acf-plugin","tag-advacned-custom-fields","tag-automattic","tag-matt-mullenweg","tag-open-source-2","tag-secure-custom-fields","tag-wordpress-controversy","tag-wordpress-com","tag-wordpress-org","tag-wp-engine","tag-wp-engine-ban","tag-wp-engine-vs-matt-mullenweg"],"_links":{"self":[{"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/posts\/5223"}],"collection":[{"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/comments?post=5223"}],"version-history":[{"count":2,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/posts\/5223\/revisions"}],"predecessor-version":[{"id":5227,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/posts\/5223\/revisions\/5227"}],"wp:attachment":[{"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/media?parent=5223"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/categories?post=5223"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ultimatewb.com\/blog\/wp-json\/wp\/v2\/tags?post=5223"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}