←back to thread

221 points michaelcampbell | 2 comments | | HN request time: 0.001s | 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 #
1. Atotalnoob ◴[] No.41831371[source]
Photomatt aka Matt mullenweg hangs out on HN.

I’d love to hear how he justifies taking away this engineers’ Sunday? I doubt this person is the only person working this weekend due to Matt’s theft of ACF

replies(1): >>41831649 #
2. usea ◴[] No.41831649[source]
> I’d love to hear how he justifies taking away this engineers’ Sunday?

His posts on slack [1] show that he sees it as "either with us or against us", and he's willing to harm users to force them to choose a side instead of staying neutral. He probably hopes that people will blame WP Engine for it.

I think his real goal is tortious interference. Hurting devs who use ACF is just a bonus.

[1] https://threadreaderapp.com/thread/1843963052183433331.html