←back to thread

ACF Plugin no longer available on WordPress.org

(www.advancedcustomfields.com)
221 points michaelcampbell | 1 comments | 13 Oct 24 15:44 UTC | HN request time: 0.204s | source
Show context
system2 ◴[13 Oct 24 19:15 UTC] No.41830709[source]▶
Oh god, this gave me a minor heart attack. We are using over 20 ACF fields for 150+ sites. I thought it was completely out of the WordPress ecosystem. I am glad they have the zip download and continuing auto updates.

EDIT: I confirm our ACF plugins on sites are all switched to secure custom fields. This is so shady, it broke our snippets because we are using prepend and append texts to wrap our field values. Now they are all broken and we have to update all our sites (also our client's sites). Let's see what comes next...

EDIT2: There goes my Sunday. I received our first ticket regarding broken homepage widgets. I have to sit down and update every site one by one. Thank you Matt Mullenweg for ruining my Sunday plans.

replies(13): >>41830770 #>>41831019 #>>41831125 #>>41831219 #>>41831312 #>>41831371 #>>41831420 #>>41831589 #>>41831598 #>>41831645 #>>41832233 #>>41833738 #>>41835660 #
1. mldevv ◴[13 Oct 24 21:12 UTC] No.41831645[source]▶
(community member, not affiliated with WP, WPE, or A8C)

I can confirm this has been escalated internally in the WP slack.

I can also provide this context which I found concerning, given the way this was taken over and rolled out on a Saturday afternoon, of which I have also been dragged into now as a fellow site maintainer.

- Matt Mullenweg "in a few days we'll have a Github where people can get involved, and we can also set up proper build systems, etc"

So its all in flux obviously. I let them know the same thing, that I find this as a malicious supply chain attack that is affecting the community.