Advanced Custom Fields (ACF) Now Secure Custom Fields-2

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?si=jgNKVJk7cfYwncys&v=gqGLnpG07Z8&feature=youtu.be) > [!note]+ Document Notes > tags: [#WordPress, #plugin-management, #ACF] > Author: Paul C > Source: YouTube > Reference: [Advanced Custom Fields Now Secure Custom Fields](https://www.youtube.com/watch?v=gqGLnpG07Z8) > date created: {{2024-10-14}} {{14:30}} > > # Title: Advanced Custom Fields (ACF) Now Secure Custom Fields (SCF) >  ## 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 video discusses the sudden forking of Advanced Custom Fields (ACF) by WordPress.org into a new plugin called Secure Custom Fields (SCF). This change affects the management of ACF, stripping out upsells from the WP Engine version and raising concerns about the long-term support and development paths. ## 📖 Main Content: The fork has resulted in confusion, as the new SCF replaces ACF in many instances without user consent. WP Engine continues to maintain ACF independently with all its premium features, but users must manually switch back to avoid discrepancies. ### 🗒️ Notes: - **Fork Announcement**: WordPress.org has taken over ACF, renaming it SCF. - **SCF vs ACF**: SCF removes WP Engine upsells, targeting a security concern. - **Manual Update Recommended**: Users must install ACF directly from WP Engine if they wish to retain the original features. - **Impact on Users**: Current installations will receive SCF by default, potentially causing conflicts.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. ## 🗣️ Paraphrase: 1. WordPress.org has replaced ACF with a forked version called SCF, removing all upsells to focus on security. 2. Users are encouraged to download ACF manually to maintain the plugin's original functionality as the future of SCF is uncertain. ## 📰 Newsletter: Big news for WordPress users—ACF has been replaced by SCF on WordPress.org. SCF removes upsells, focusing on security fixes. If you're using ACF and want the original features, download it from WP Engine to avoid disruption. Keep an eye on this transition, as it impacts millions of sites! ## ✅ Action Items: - Inform teams about the SCF fork and recommend manual updates to ACF from WP Engine. - Monitor developments around SCF to stay updated on any changes. ## 🧪 Hypotheses: - ACF users switching to SCF may encounter compatibility issues. - Forking ACF will create pressure on WP Engine to enhance premium offerings. ### 📊 Methodology: - **Surveys**: Collect feedback from ACF users post-fork. - **Usage Data**: Track adoption of SCF vs. ACF over time. ### ❓ Questions: - Will SCF and ACF develop in parallel, or will SCF be phased out? - How will WP Engine incentivize users to stick with ACF? ### 🔮 Future Research: - Investigate whether forking ACF impacts user trust in WordPress.org plugins. ### 💡 Implications: The forking of ACF could disrupt plugin management practices, affecting developers and site owners alike. ### 🧠 Learning Styles Assessment: - **Visual**: Comparison charts between SCF and ACF. - **Aural**: Podcast episode explaining the implications. - **Kinesthetic**: Guide for manually updating ACF. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure all documentation is accessible. - **Keyboard Navigation**: Optimize ACF settings for accessibility. ### 🌍 DEIB Assessment: - **Inclusive Language**: Simplify plugin documentation for non-technical users. ### ✅ Logical Validity: - **Strength**: The recommendation to manually install ACF ensures continuity. - **Weakness**: The video assumes users are aware of the fork, which may not be the case. ### 🔍 SEO Evaluation: - **Keywords**: SCF, ACF, WordPress plugin management. - **Optimization**: Improve visibility with targeted documentation. ## 🎯 Conclusion: This sudden change highlights the complexities of plugin management in the WordPress ecosystem. Users must act quickly to avoid disruptions by manually switching back to ACF from WP Engine, ensuring their sites remain stable and functional.  📄 **Full text:** ![[Full Document Contents/Articles/Advanced Custom Fields (ACF) Now Secure Custom Fields-2|Advanced Custom Fields (ACF) Now Secure Custom Fields, WP Minute - Learn WordPress]] ## Highlights - 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/01ja9epzk9kaaenabad9m63k6a))