Is ACF 6.3.8 (free) actually SCF now? WordPress is telling me I already have SCF “active” even though it’s not showing as a separate plugin on the plugin page.
Copyright Ā© 2020 - 2022, Project DMC - WordPress Tutorials for Beginners- All Rights Reserved. Privacy Policy
Yes they hijacked it, including the slug.
Here is what you can do if you want the original ACF, as per the plugin author: [https://www.advancedcustomfields.com/blog/acf-plugin-no-longer-available-on-wordpress-org/](https://www.advancedcustomfields.com/blog/acf-plugin-no-longer-available-on-wordpress-org/)
It’s using the ACF plugin slug so functionally yes, it is ACF.
In effect, Matt has executed a supply chain attack and is somehow proud of it?
Iād recommend removing the petty-ware and go direct to ACFs website to get the latest version and moving forward new versions will come from their own git repo
Y’all remember when u/photomatt railed against WPEngine because it’s “confusing users”? Pepperidge farm remembers.
No actually, it is *not*. What you are seeing in the screenshot is an active install of actual Advanced Custom Fields (ACF) 6.3.8. Because the listing of ACF has been overwritten by the [wordpress.org](http://wordpress.org) team, by Secure Custom Fields (SCF), they share the *same* slug (`advanced-custom-fields` bit of the URL). Because WordPress (the software itself) checks a plugin being active by the slug, it will tell you that SCF is already active when you try to install ACF – and the other way around, exactly the same.
The only difference that you’ll see soon enough is that ACF is actually called ‘Advanced Custom Fields’ in the list of plugins (as shown in your first screenshot), while SCF will be called ‘Secure Custom Fields’.
they can’t even search and replace the name with their new Stolen Custom Fields name š
https://wordpress.org/support/plugin/advanced-custom-fields/reviews/
Yes SCF is ACF now.