Mullenweg and Co. Take Over the Advanced Custom Fields Plugin  🔗 **Source:** [Mullenweg and Co. Take Over the Advanced Custom Fields Plugin](https://wpshout.com/mullenweg-takes-over-advanced-custom-fields/) > [!note]+ Document Notes > tags: [#wordpress, #plugin, #opensource, #conflict, #ACF] > Author: Multiple Sources > Source: WP Tavern, The WP Minute, Geek News Central, Techzine Global > Reference: [ACF Fork Conflict](https://wptavern.com), [WordPress Takes Control](https://geeknewscentral.com) > date created: 2024-10-15 09:00 > > # Title: Mullenweg Takes Over Advanced Custom Fields Plugin > <!-- deep-read:sections start --> ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ## 📝 Summary: The acquisition of Advanced Custom Fields (ACF) by WordPress.org, initiated by Matt Mullenweg, has sparked a heated conflict with WP Engine. ACF is a popular plugin that allows advanced customization of edit screens in WordPress. In a controversial move, Mullenweg announced a new version of the plugin, "Secure Custom Fields," citing the need to address security concerns and remove commercial upsells. ## 📖 Main Content: This conflict is tied to ongoing disputes between WP Engine and Automattic, Mullenweg’s company. WP Engine, which previously managed ACF, has expressed frustration, accusing Mullenweg of forcibly taking over the plugin without consent. Mullenweg justified the takeover by referencing WordPress.org’s plugin guidelines, which allow unilateral action to address security issues. WP Engine responded by moving plugin updates to its own platform, bypassing WordPress.org's distribution channels. Meanwhile, WordPress.org enabled automatic updates to switch users from ACF to the newly created Secure Custom Fields plugin, further complicating the situation for site owners. ### 🗒️ Notes: - **Mullenweg's Justification:** Security concerns and removal of commercial elements. - **WP Engine’s Response:** Updates now managed outside of WordPress.org. - **ACF Community Impact:** Criticism from the ACF team about forced action. - **WordPress Ecosystem Effects:** Growing frustration with Mullenweg’s leadership style. ## 🗣️ Paraphrase: 1. **Original:** Mullenweg explained that the new Secure Custom Fields would remove problematic commercial upsells and address security issues. **Paraphrase:** Mullenweg highlighted that Secure Custom Fields was introduced to eliminate monetization practices and resolve potential vulnerabilities in the original plugin. 2. **Original:** WP Engine has shifted updates for ACF to their own infrastructure to maintain control and continuity. **Paraphrase:** To ensure users receive consistent updates, WP Engine has transferred ACF’s update management to its independent platform. ## 📰 Newsletter: In this edition, we're diving into the controversy around Advanced Custom Fields (ACF). WordPress.org recently took control of the ACF plugin, rebranding it as Secure Custom Fields, sparking backlash from WP Engine. This move raises questions about plugin governance and the future of open-source collaborations. Keep your site secure by following the latest updates from both WordPress.org and WP Engine. For developers, this conflict underscores the importance of monitoring how plugin management changes can impact projects. Stay informed to ensure smooth operations on your WordPress sites. ## ✅ Action Items: 1. Align the situation with advocacy goals: This case exemplifies the need for clearer governance in open-source communities. 2. Discuss governance issues in upcoming events and newsletters to engage the WordPress community in meaningful dialogue. 3. Monitor the ACF fork’s reception to understand its impact on the open-source ecosystem. ## 🧪 Hypotheses: - **Hypothesis 1:** Centralized control over plugins may reduce developer participation in the WordPress ecosystem. - **Hypothesis 2:** Transitioning plugin updates away from WordPress.org could enhance security and autonomy. ## 📊 Methodology: - **Data Sources:** WordPress.org forums, social media reactions, plugin analytics. - **Design:** Mixed-methods analysis, combining surveys with plugin adoption rates. - **Techniques:** Sentiment analysis of community feedback. ## ❓ Questions: 1. How will this conflict influence the adoption of Secure Custom Fields? 2. Will WP Engine’s decision to manage updates independently become a trend? ## 🔮 Future Research: - Explore the impact of forced plugin forks on open-source collaboration. - Investigate how plugin autonomy affects security and adoption rates. ## 💡 Implications: The ongoing conflict highlights a need for transparent governance. How WordPress.org navigates this situation may set a precedent for future community decisions. ## 🧠 Learning Styles Assessment: - **Visual:** Diagrams showing ACF usage would enhance understanding. - **Aural:** Podcasts discussing governance would help auditory learners. - **Kinesthetic:** Encourage hands-on exploration with Secure Custom Fields. - **Logical:** Offer tutorials with step-by-step instructions on plugin updates. ## 📊 Accessibility Assessment: - **Improvement Needed:** Ensure Secure Custom Fields documentation includes alt text for diagrams. - **Enhancements:** Improve keyboard navigation on the plugin’s new documentation page. ## 🌍 DEIB Assessment: - **Inclusivity:** Include diverse voices from the WordPress community. - **Neurodiversity:** Use clear and concise language to aid comprehension. ## ✅ Logical Validity: The arguments for forking ACF are logically framed around security, but they lack transparency regarding the specific issues involved. The move has been criticized for lacking community input, raising questions about governance ethics. ## 🔍 SEO Evaluation: - **Keywords:** “Advanced Custom Fields,” “Secure Custom Fields,” “WordPress plugin management.” - **Meta Description:** Adjust for relevance by including keywords about governance and plugin security. - **Internal Links:** Connect to other governance-related WordPress topics. ## 🎯 Conclusion: The ACF fork reflects deeper tensions around plugin governance, control, and collaboration within the WordPress community. As the situation unfolds, it offers valuable lessons about balancing open-source ideals with practical realities. <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Mullenweg and Co. Take Over the Advanced Custom Fields Plugin|Mullenweg and Co. Take Over the Advanced Custom Fields Plugin, Colin Newcomer]] ## Highlights - If a user automatically updates Advanced Custom Fields through their WordPress dashboard, the plugin will change to Secure Custom Fields, which kind of makes it seem more like a malicious supply chain attack than a “fork.” ([View Highlight](https://read.readwise.io/read/01ja86v7ykfrbgvfcva0xdjskk))