←back to thread

221 points michaelcampbell | 1 comments | | HN request time: 0.197s | source
Show context
system2 ◴[] 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 #
foosantos ◴[] No.41833738[source]
I've been monitoring the SCF forums as well on WPorg, and there have been no reports of issues since moving to SCF.

It would be fantastic if people could open a topic there or a thread on Slack if they face any issues.

replies(4): >>41833740 #>>41835319 #>>41842233 #>>41845242 #
1. tone ◴[] No.41835319[source]
No one should risk an unknown entity taking illegal control of a key plugin on their site. I can't imagine anyone wanting WP.org to weaponize more plugins on their site.

Update ACF and stay secure against this latest threat. https://www.advancedcustomfields.com/blog/installing-and-upg...