Advisory: Advanced Custom Fields Changes  🔗 **Source:** [Advisory: Advanced Custom Fields Changes](https://timnash.co.uk/advisory-advanced-custom-fields-changes/) > [!note]+ Document Notes > tags: [#wordpress, #security, #plugin, #legaldispute] > Author: Tim Nash > Source: [Tim Nash’s Blog](https://timnash.co.uk) > Reference: [Advisory: Advanced Custom Fields changes](https://timnash.co.uk/advisory-advanced-custom-fields-changes/) > date created: 2024-10-14 11:15 > > # Title: Advisory on ACF Changes and Legal Risks > <!-- 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-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ## 📝 Summary: This advisory discusses how WordPress.org replaced Advanced Custom Fields (ACF) with Secure Custom Fields (SCF) following legal disputes with WP Engine. Although WP Engine maintains an alternative ACF version, Nash warns users about unexpected updates. Both SCF and ACF offer the same security patch, but governance questions remain unresolved. ## 📖 Main Content: WordPress.org pushed SCF, stripping ACF's branding and replacing it on the plugin repository without user notice. While WP Engine mirrors ACF independently, some users may encounter unintended updates to SCF. The article highlights governance issues within WordPress and provides recommendations to maintain ACF from WP Engine if desired. ### 🗒️ Notes: - **Update Impact**: ACF was replaced with SCF via automatic updates. - **Governance Issues**: Concerns over WordPress's unilateral decision-making. - **Security Patch**: Both SCF and ACF contain identical fixes, suggesting the change was not security-driven. ## 📖 References: - [Advisory on ACF Changes](https://timnash.co.uk/advisory-advanced-custom-fields-changes/) ## 🗣️ Paraphrase: 1. Tim Nash explains that SCF and ACF share the same security patch, raising questions about the necessity of WordPress’s intervention. 2. Users relying on WP Engine’s mirrored version of ACF must take extra steps to prevent unintentional upgrades to SCF. ## 📰 Newsletter: **Heads up!** If you're using Advanced Custom Fields (ACF), you might notice some changes—WordPress.org has replaced ACF with Secure Custom Fields (SCF) amid ongoing disputes with WP Engine. The plugins share identical security fixes, but governance questions are sparking debate. Get the full scoop, plus tips to manage plugin updates effectively, in this week’s newsletter! ## ✅ Action Items: - **Professional Alignment**: This issue reflects the importance of governance transparency, aligning with your open-source advocacy work. - **OSPO Goal**: Navigating these governance challenges builds essential knowledge for your future OSPO ambitions. ## 🧪 Hypotheses: - Frequent governance conflicts could drive developers to seek decentralized plugin platforms. - Similar incidents may result in increased user preference for direct vendor support. ### 📊 Methodology: - **Survey**: Collect feedback on plugin management practices from the WordPress community. - **Case Study**: Compare plugin governance models across other open-source ecosystems. ### ❓ Questions: - How can developers safeguard their plugins from unexpected governance actions? - What governance reforms could improve transparency in the WordPress ecosystem? ### 🔮 Future Research: - Assess how governance conflicts affect developer participation. - Explore how decentralized governance could prevent similar disputes. ### 💡 Implications: Governance improvements may strengthen developer trust and encourage long-term contributions to open-source projects. ### 🧠 Learning Styles Assessment: - **Visual Learners**: Include a visual timeline of the SCF update process. - **Logical Learners**: Add a side-by-side comparison of ACF and SCF updates. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure all plugin documentation is accessible. - **Keyboard Navigation**: Optimize plugin update workflows for accessibility. ### 🌍 DEIB Assessment: - **Inclusiveness**: Encourage inclusive decision-making in plugin governance. - **Psychological Safety**: Promote open dialogue among contributors regarding governance changes. ### ✅ Logical Validity: - **Strengths**: Nash provides clear evidence of identical security patches, questioning WordPress’s reasoning. - **Fallacies**: Some reliance on slippery slope concerns about future governance decisions. ### 🔍 SEO Evaluation: - **Keywords**: ACF plugin, Secure Custom Fields, WordPress governance. - **Optimization**: Link to plugin documentation for improved engagement. ## 🎯 Conclusion: The ACF to SCF transition raises critical concerns about governance and user trust within WordPress. As plugin management remains in flux, this case underscores the need for transparent decision-making processes to maintain community confidence. <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/Advisory Advanced Custom Fields Changes|Full Document Contents]] ## Document Notes --- tags: #wordpress #security #plugin #legaldispute Author: Tim Nash Source: [Tim Nash’s Blog](https://timnash.co.uk) Reference: [Advisory: Advanced Custom Fields changes](https://timnash.co.uk/advisory-advanced-custom-fields-changes/) date created: 2024-10-14 11:15 --- # Title: Advisory on ACF Changes and Legal Risks ## Table of Contents: - [[#📝 Summary:]] - [[#📖 Main Content:]] - [[#🗒️ Notes:]] - [[#🗣️ Paraphrase:]] - [[#📰 Newsletter:]] - [[#✅ Action Items:]] - [[#🧪 Hypotheses:]] - [[#📊 Methodology:]] - [[#❓ Questions:]] - [[#🔮 Future Research:]] - [[#💡 Implications:]] - [[#🧠 Learning Styles Assessment:]] - [[#📊 Accessibility Assessment:]] - [[#🌍 DEIB Assessment:]] - [[#✅ Logical Validity:]] - [[#🔍 SEO Evaluation:]] - [[#🎯 Conclusion:]] ## 📝 Summary: This advisory discusses how WordPress.org replaced Advanced Custom Fields (ACF) with Secure Custom Fields (SCF) following legal disputes with WP Engine. Although WP Engine maintains an alternative ACF version, Nash warns users about unexpected updates. Both SCF and ACF offer the same security patch, but governance questions remain unresolved. ## 📖 Main Content: WordPress.org pushed SCF, stripping ACF's branding and replacing it on the plugin repository without user notice. While WP Engine mirrors ACF independently, some users may encounter unintended updates to SCF. The article highlights governance issues within WordPress and provides recommendations to maintain ACF from WP Engine if desired. ### 🗒️ Notes: - **Update Impact**: ACF was replaced with SCF via automatic updates. - **Governance Issues**: Concerns over WordPress's unilateral decision-making. - **Security Patch**: Both SCF and ACF contain identical fixes, suggesting the change was not security-driven. ## 📖 References: - [Advisory on ACF Changes](https://timnash.co.uk/advisory-advanced-custom-fields-changes/) ## 🗣️ Paraphrase: 1. Tim Nash explains that SCF and ACF share the same security patch, raising questions about the necessity of WordPress’s intervention. 2. Users relying on WP Engine’s mirrored version of ACF must take extra steps to prevent unintentional upgrades to SCF. ## 📰 Newsletter: **Heads up!** If you're using Advanced Custom Fields (ACF), you might notice some changes—WordPress.org has replaced ACF with Secure Custom Fields (SCF) amid ongoing disputes with WP Engine. The plugins share identical security fixes, but governance questions are sparking debate. Get the full scoop, plus tips to manage plugin updates effectively, in this week’s newsletter! ## ✅ Action Items: - **Professional Alignment**: This issue reflects the importance of governance transparency, aligning with your open-source advocacy work. - **OSPO Goal**: Navigating these governance challenges builds essential knowledge for your future OSPO ambitions. ## 🧪 Hypotheses: - Frequent governance conflicts could drive developers to seek decentralized plugin platforms. - Similar incidents may result in increased user preference for direct vendor support. ### 📊 Methodology: - **Survey**: Collect feedback on plugin management practices from the WordPress community. - **Case Study**: Compare plugin governance models across other open-source ecosystems. ### ❓ Questions: - How can developers safeguard their plugins from unexpected governance actions? - What governance reforms could improve transparency in the WordPress ecosystem? ### 🔮 Future Research: - Assess how governance conflicts affect developer participation. - Explore how decentralized governance could prevent similar disputes. ### 💡 Implications: Governance improvements may strengthen developer trust and encourage long-term contributions to open-source projects. ### 🧠 Learning Styles Assessment: - **Visual Learners**: Include a visual timeline of the SCF update process. - **Logical Learners**: Add a side-by-side comparison of ACF and SCF updates. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure all plugin documentation is accessible. - **Keyboard Navigation**: Optimize plugin update workflows for accessibility. ### 🌍 DEIB Assessment: - **Inclusiveness**: Encourage inclusive decision-making in plugin governance. - **Psychological Safety**: Promote open dialogue among contributors regarding governance changes. ### ✅ Logical Validity: - **Strengths**: Nash provides clear evidence of identical security patches, questioning WordPress’s reasoning. - **Fallacies**: Some reliance on slippery slope concerns about future governance decisions. ### 🔍 SEO Evaluation: - **Keywords**: ACF plugin, Secure Custom Fields, WordPress governance. - **Optimization**: Link to plugin documentation for improved engagement. ## 🎯 Conclusion: The ACF to SCF transition raises critical concerns about governance and user trust within WordPress. As plugin management remains in flux, this case underscores the need for transparent decision-making processes to maintain community confidence. ## Highlights - However, if you have automatic updates enabled, you might have noticed a surprise: *ACF* has already been replaced with *Secure Custom Fields* (SCF). ([View Highlight](https://read.readwise.io/read/01ja5p6gac3af4chnh4968a45y))