Invoking point 18 of the plugin directory guidelines, we are introducing Secure Custom Fields (SCF), a free fork and drop-in replacement of the Advanced Custom Fields (ACF) plugin. You can safely uninstall ACF and activate SCF from the #WordPresswordpress.org/news/2024/10...
On behalf of the WordPress security team, I am announcing that we are invoking point 18 of the plugin directory guidelines and are forking Advanced Custom Fields (ACF) into a new plugin, Secure Cus…
That's disingenuous. The problem was only caused by you when you previously removed access from the developers. In this way, you consciously and intentionally prevented the developers from being able to fix a problem and upload an update that additionally was considered to be less dangerous.
So happy to no longer be working on any WordPress sites. This ridiculous aggression by Matt is so toxic to that community. On the plus side, I expect this to accelerate interest in non-WP open source CMSes by a ton!
☝️🤓 Invoking point 18 of the plugin directory guidelines
When are you going to do this for WPGraphQL, which has been using a publicly known vulnerable third-party library for 18 months?
Please, don't do that. You are breaking the community credibility. Do the fork, create another version of the plugin, but don't take over the slug directory. You know this is not reasonable, the ACF developers and any affiliate are not allowed to access WP org repository.
Nobody here is gonna buy this nonsense. Stop attacking developers and users, Matt.
😬 not a good look. De-escalate. This should all have taken a different path, with Matt’s keynote being to lay out new community contribution rules, starting a period of consultation, agreeing, and _then_ enforcing. Not this mafia style war. Be mature. Pause & reset, or it damages everyone
What are you doing????