Advanced Custom Fields (ACF) Now Secure Custom Fields ![rw-book-cover](https://i.ytimg.com/vi/gqGLnpG07Z8/maxresdefault.jpg) 🔗 **Source:** [Advanced Custom Fields (ACF) Now Secure Custom Fields](https://www.youtube.com/watch?v=gqGLnpG07Z8) > [!note]+ Document Notes > tags: [#wordpress, #open-source, #community, #plugins] > Author: [YouTube Transcript] > Source: [YouTube](https://www.youtube.com/watch?v=gqGLnpG07Z8) > Reference: [Transcript provided in the prompt] > date created: 2024-10-14 18:00 > > # Title: ACF Becomes SCF: WordPress, WP Engine, and the Plugin Takeover Controversy > <!-- deep-read:sections start --> ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📖 References](#-references) - [🗣️ 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: This note discusses the recent controversy surrounding the Advanced Custom Fields (ACF) plugin, now rebranded as Secure Custom Fields (SCF) by WordPress.org. The takeover, justified by WordPress as a security measure, has stirred significant backlash. The video highlights concerns about governance, commercial influence, and the implications for the open-source community. --- ## 📖 Main Content: The ACF-to-SCF takeover exemplifies tensions between open-source principles and commercial interests. WP Engine’s influence over ACF was removed by WordPress.org in what many see as an unprecedented move. This decision has sparked concerns about fairness, transparency, and community trust. ### 🗒️ Notes - **Background**: - ACF, owned by WP Engine, became a focus of WordPress governance conflict. - WordPress.org cited security issues to justify the rebranding of ACF as SCF. - **Takeover Impact**: - SCF replaced ACF within WordPress, stripping commercial upsells but retaining core functionality. - The original ACF can still be accessed from external sources, though confusion persists. - **Community Response**: - Developers expressed outrage over the lack of consent and transparency in the plugin fork. - Legal disputes between WP Engine and WordPress remain unresolved, adding uncertainty. --- ## 📖 References: - [YouTube Video](https://www.youtube.com/watch?v=gqGLnpG07Z8) --- ## 🗣️ Paraphrase: 1. **Original**: "WordPress.org forked ACF into SCF, removing commercial upsells but keeping the core functionality intact." - **Paraphrase**: WordPress rebranded ACF as SCF, eliminating paid features but preserving the essential plugin structure. 2. **Original**: "Developers criticized WordPress.org for taking control of ACF without permission, calling the action unprecedented." - **Paraphrase**: Many in the developer community condemned WordPress for seizing control of ACF, an act they view as without precedent. --- ## 📰 Newsletter: 📢 **Latest WordPress News**: The WordPress community is buzzing with reactions after WordPress.org took control of the popular ACF plugin, rebranding it as Secure Custom Fields (SCF). While the move aims to enhance security, developers are raising concerns about transparency and governance. Stay informed about the unfolding legal battles and what this means for open-source plugins. Plus, check out our latest recommended tools and plugins to power your WordPress site [here](https://wordpress.org). --- ## ✅ Action Items: - **Professional Alignment**: - Explore governance models that address transparency and accountability in open-source projects. - Highlight how incidents like the ACF takeover can inform sustainable plugin development. - Engage with community discussions to reinforce open-source advocacy. --- ## 🧪 Hypotheses: 1. The ACF/SCF conflict may prompt WordPress to formalize governance rules. 2. Similar governance issues could emerge in other open-source ecosystems. ### 📊 Methodology: - **Data Sources**: WordPress forums, plugin repositories, legal filings. - **Design**: Case study approach with sentiment analysis of community reactions. --- ### ❓ Questions: 1. How can WordPress prevent governance conflicts in the future? 2. What role should community feedback play in plugin management decisions? --- ### 🔮 Future Research: - Investigate best practices for plugin governance in open-source platforms. - Examine the long-term effects of the ACF/SCF takeover on community trust. --- ### 💡 Implications: - Stronger governance mechanisms could emerge from this controversy, shaping future open-source projects. - The community may push for more transparent decision-making processes. --- ### 🧠 Learning Styles Assessment: - **Visual Learners**: Add flowcharts showing the ACF-SCF timeline. - **Aural Learners**: Provide podcast episodes discussing plugin governance. - **Kinesthetic Learners**: Offer practical workshops on conflict resolution in open-source communities. --- ### 📊 Accessibility Assessment: - **Screen Readers**: Ensure key announcements have alt-text for screen readers. - **Keyboard Navigation**: Optimize plugin repositories for seamless navigation. --- ### 🌍 DEIB Assessment: - **Cultural Relevance**: Include insights from diverse plugin developers. - **Inclusive Language**: Avoid jargon, ensuring the content is accessible to all users. --- ### ✅ Logical Validity: - **Sound Reasoning**: The need for security updates supports the SCF rebranding decision. - **Fallacy Detected**: Some arguments rely on emotional appeals, detracting from objectivity. --- ### 🔍 SEO Evaluation: - **Keywords**: "ACF plugin takeover," "SCF WordPress governance." - **Meta Description**: “Learn about the ACF to SCF rebranding and its impact on WordPress governance.” --- ## 🎯 Conclusion: The ACF-to-SCF transition highlights critical governance challenges within the WordPress community. As developers and platform leaders grapple with these issues, the resolution of this conflict may set important precedents for the future of open-source projects. Short Summary for [Advanced Custom Fields (ACF) now Secure Custom Fields (SCF)](https://www.youtube.com/watch?v=gqGLnpG07Z8) by [Merlin](https://merlin.foyer.work/) WordPress Forks Advanced Custom Fields to Secure Custom Fields: New Plugin Ensures Security, Removes Upsells, and Addresses Recent Issues. [00:04](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=4) ACF renamed to SCF with enhanced security measures. [00:49](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=49) Recent versions of ACF may show up as SCF in WordPress admin [01:41](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=101) ACF is rebranded as SCF for security reasons [02:29](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=149) Transition from ACF to SCF is uncertain [03:11](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=191) Secure Custom Fields (SCF) removes premium upsells [03:53](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=233) Secure Custom Fields removes commercial upsells from Advanced Custom Fields plugin. [04:50](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=290) ACF has been rebranded as Secure Custom Fields by wordpress.org team. [05:34](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=334) ACF is now SCF with implications --------------------------------- Detailed Summary for [Advanced Custom Fields (ACF) now Secure Custom Fields (SCF)](https://www.youtube.com/watch?v=gqGLnpG07Z8) by [Merlin](https://merlin.foyer.work/) WordPress Forks Advanced Custom Fields to Secure Custom Fields: New Plugin Ensures Security, Removes Upsells, and Addresses Recent Issues. [00:04](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=4) ACF renamed to SCF with enhanced security measures. - WordPress.org announced forking ACF into SCF to adhere to guidelines and address security issues. - SCF has eliminated commercial upsells and resolved security vulnerabilities. [00:49](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=49) Recent versions of ACF may show up as SCF in WordPress admin - Creators of ACF claim it was taken away without consent in history of WordPress - You can still get ACF from Advanced custom fields.com and follow installation guidelines [01:41](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=101) ACF is rebranded as SCF for security reasons - The fork is also a security guideline - It's a direct takeover and all active installs will receive SCF [02:29](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=149) Transition from ACF to SCF is uncertain - SCF might go back to WordPress repo through legal procedures - The current listing of SCF resembles ACF visually and functionally [03:11](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=191) Secure Custom Fields (SCF) removes premium upsells - ACF branding remains, but premium upsells are removed - ACF logo and links still direct to Advanced Custom Fields documentation [03:53](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=233) Secure Custom Fields removes commercial upsells from Advanced Custom Fields plugin. - Secure Custom Fields operates as a stripped down version of Advanced Custom Fields, without upsells. - By activating the official Advanced Custom Fields plugin, you'll encounter upsells and banners for extra features and WP Engine hosting. [04:50](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=290) ACF has been rebranded as Secure Custom Fields by wordpress.org team. - The rebranded version does not have any ACF upsells and has removed WP engine commercial upsell stuff. - It is uncertain whether the rebranded version will continue to be developed with new features in the future. [05:34](https://www.youtube.com/watch?v=gqGLnpG07Z8&t=334) ACF is now SCF with implications - The implications of the ACF becoming SCF will depend on the outcome of the lawsuit and the future development of SCF. - Keep updated for any changes or developments in the ACF and SCF situation, as it may lead to a replacement for ACF. <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Advanced Custom Fields (ACF) Now Secure Custom Fields|Advanced Custom Fields (ACF) Now Secure Custom Fields, WP Minute - Learn WordPress]] ## Highlights - look at secure custom fields in a bit of an unprecedented announcement from wordpress.org this blog post written by Matt mullenweg quote on behalf of the WordPress security team I am announcing that we are invoking 18 of the plug-in directory guidelines and forking Advanced custom Fields ACF into a new plugin secure custom Fields SCF has been updated to remove commercial upsells and fix a security problem ([View Highlight](https://read.readwise.io/read/01ja6jejkjj978zhv5hezzenqf))