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.2s | 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]▶

>>41829400 #

And this is different from WP Engine modifying Wordpress exactly how?

replies(5): >>41830878 #>>41830881 #>>41831521 #>>41831850 #>>41832338 #

1. FireBeyond ◴[13 Oct 24 21:36 UTC] No.41831850[source]▶

>>41830865 #

Let's be really, really clear here.

Matt might pontificate about "bastardizing and messing with" WordPress, but this is what he is actually referring to:

A. Single. Configuration. Option.

A. Changed. Default.

Post revisions are a configuration option in the admin panel. They are enabled by default. Some hosting providers (and I expect WPE is not the only one) set it to disabled by default.

That's it.

This is not remotely comparable.

Even without the ACF situation, Matt's description of WPE bastardizing the fundamental offering of WordPress is asinine at best, actively deceptive at worst (and that's where we seem to be, so far).

↑