←back to thread

ACF Plugin no longer available on WordPress.org

(www.advancedcustomfields.com)
221 points michaelcampbell | 10 comments | 13 Oct 24 15:44 UTC | HN request time: 1.455s | source | bottom
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. n3storm ◴[13 Oct 24 20:30 UTC] No.41831312[source]▶
pass the bill to matt when you finish fixing those broken wp.
replies(2): >>41831412 #>>41833808 #
2. znpy ◴[13 Oct 24 20:42 UTC] No.41831412[source]▶
He will reply that go has just “contributed their fair share of man-hours” /s
3. photomatt ◴[14 Oct 24 02:55 UTC] No.41833808[source]▶
I don't think anything about our update could cause the issues he describes and we've had no other reports, this is the only claim on the internet, and doesn't include enough technical details to tell if it's an actual bug or not.

If it's a bug, our bad and we'll fix ASAP. If it's a bug, it's a very rare one. There have been 225k downloads of the SCF plugin in the past 24 hours, implying a lot of updates. I would estimate at least 60% of the sites with auto-upgrade on and using .org for updates have done so already. https://wordpress.org/plugins/advanced-custom-fields/advance...

That said, I'm happy to pay system2 whatever he thinks his time was "spent" on a Sunday is worth. Just let me know an amount and where to send. You can contact me here: https://ma.tt/contact/ .

replies(4): >>41833913 #>>41835456 #>>41865097 #>>41886700 #
4. hashim-warren ◴[14 Oct 24 03:20 UTC] No.41833913[source]▶
Matt, you say that you've had no other reports and this is the only claim on the Internet.

That's not true. You have users on the support forums reporting issues with SCF.

"this has caused an incident requiring unschedule maintenance on a weekend. I use this plugin on a couple hundred sites I help maintain, so this has been a very bad experience "

https://wordpress.org/support/topic/plugin-hijacked-on-weeke...

5. ChrisAntaki ◴[14 Oct 24 08:28 UTC] No.41835456[source]▶
Thanks for improving on ACF. The plugin went downhill after the creator stepped away, IMO.

A while back, I bought a lifetime "Pro" license for ACF. It worked great for years. The last few times I tried ACF though, the admin experience felt degraded. My impression was their early customers had become an afterthought.

Looking forward to trying SCF. I have higher hopes for the plugin now.

replies(1): >>41835733 #
6. ChrisAntaki ◴[14 Oct 24 09:34 UTC] No.41835822{4}[source]▶
Hi account with no other comments, no submissions, and no favorites, after registering 5+ years ago
replies(1): >>41840533 #
7. mrdoe ◴[14 Oct 24 18:43 UTC] No.41840533{5}[source]▶
My time has come, I will not lurk anymore. Where are the pitchforks btw?
replies(1): >>41847147 #
8. ndndjdjdn ◴[15 Oct 24 10:41 UTC] No.41847147{6}[source]▶
Wot. Everyone has an old throwaway?
9. throw16180339 ◴[16 Oct 24 23:54 UTC] No.41865097[source]▶
> I don't think anything about our update could cause the issues he describes and we've had no other reports, this is the only claim on the internet, and doesn't include enough technical details to tell if it's an actual bug or not.

Don't gaslight us. You've been removing negative reviews.

10. btasker ◴[19 Oct 24 09:24 UTC] No.41886700[source]▶
> I don't think

No, you just act and screw everyone else.

There's no justification for this whatsoever - it was your actions which meant that the ACF team couldn't manage the plugin on dotorg, and the issue you fixed was unbelievably minor.

IF you even had a point in the beginning, you've fatally undermined it. Hell, WPE's motion for a preliminary injunction even now notes that your actions here have potentially fallen into CFAA territory - https://storage.courtlistener.com/recap/gov.uscourts.cand.43...

Given you've been banning dissenters from Slack, I wonder "why" people might not be reporting issues where you can see them?