←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: 0s | source
Show context
denislour ◴[13 Oct 24 16:38 UTC] No.41829400[source]▶
Wow, this is a big deal. Matt Mullenweg taking over ACF like that? Not cool. It's not just about messing with years of hard work, but think about all those WordPress sites now running code the ACF team didn't approve. Kinda scary when you think about it. Hope this doesn't become a trend in the open-source world.
replies(2): >>41830693 #>>41830865 #
TiredOfLife ◴[13 Oct 24 19:36 UTC] No.41830865[source]▶
And this is different from WP Engine modifying Wordpress exactly how?
replies(5): >>41830878 #>>41830881 #>>41831521 #>>41831850 #>>41832338 #
odo1242 ◴[13 Oct 24 19:38 UTC] No.41830881[source]▶
WP engine never modified WordPress. They took stock Wordpress and edited a configuration file to disable revisions. They didn’t actually change any code.
replies(1): >>41830899 #
mgkimsal ◴[13 Oct 24 19:41 UTC] No.41830899[source]▶
I thought they'd also modified revisions to have a limit, instead of unlimited. Even when 'enabled', it's not how the rest of the wp installs would behave (iirc). Likely there was some code change there to enable that restriction.
replies(3): >>41830956 #>>41831720 #>>41838882 #
1. mldevv ◴[13 Oct 24 21:20 UTC] No.41831720{4}[source]▶
They use the parts of wordpress that are specifically built in to make modifications, as any other site maintainer would hosting their own install.

You are mistaken.