Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ACF Plugin no longer available on WordPress.org

advancedcustomfields.com

Post reply on HN
Print view View original

11–20 of 151 posts

Re: ACF Plugin no longer available on WordPress.org

#11

Post by gg-plz »

system2 wrote: post #9

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…

As someone who doesn’t use it, were those features removed into the patch?

If they’re actively breaking people’s sites I’d hope they can get an emergency injunction ASAP, and maybe someone can start a CFAA investigation.

Re: ACF Plugin no longer available on WordPress.org

#13

Post by TiredOfLife »

denislour wrote: post #3

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.

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

Re: ACF Plugin no longer available on WordPress.org

#14

Post by mingus88 »

TiredOfLife wrote: post #13
denislour wrote: post #3

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.

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

Well, we can start with the fact that WP Engine hasn’t taken over any domain previously owned by Wordpress

Re: ACF Plugin no longer available on WordPress.org

#15

Post by odo1242 »

TiredOfLife wrote: post #13
denislour wrote: post #3

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.

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

WP engine never modified WordPress. They took stock Wordpress and edited a configuration file to disable revisions. They didn’t actually change any code.

Re: ACF Plugin no longer available on WordPress.org

#16

Post by gg-plz »

yidhsvc wrote: post #12

The official wp announcement of this said “we don’t plan on doing this to other plugins.” lol. anyone think they pinky promise? More like: build on Wordpress and unless you kiss the ring some guy named Matt will disappear your business.

https://x.com/WordPress/status/1845180576531468375

> Hey @WordPress. Are there any further plugins that we can expect to be forked?

> There are no others we're aware of at this time, but you are welcome to suggest some.

Re: ACF Plugin no longer available on WordPress.org

#17

Post by mgkimsal »

odo1242 wrote: post #15
TiredOfLife wrote: post #13

Earlier quoted context omitted.

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

WP engine never modified WordPress. They took stock Wordpress and edited a configuration file to disable revisions. They didn’t actually change any code.

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.

Re: ACF Plugin no longer available on WordPress.org

#18

Post by maxbond »

To me this is indistinguishable from an account takeover attack executed by an insider. I doubt any prosecutor would be interested, but to my eyes WordPress.org has violated the CFAA by accessing WordPress instances outside the bounds of their authorization. They were authorized to modify WordPress instances in ways ACF prescribed, not in ways of their own choosing.

I'm not saying I'd like to see Mullenweg in chains, I wouldn't. But WP.org's escalating legal exposure is really concerning. I feel like we're at risk of losing a cornerstone of the web. People are talking about a different open source CMS eating their lunch, but I think the more likely scenario is that people move to Square Space, Wix, Facebook, et cetera, and open source content management becomes niche.

Re: ACF Plugin no longer available on WordPress.org

#19

Post by odo1242 »

mgkimsal wrote: post #17
odo1242 wrote: post #15

Earlier quoted context omitted.

WP engine never modified WordPress. They took stock Wordpress and edited a configuration file to disable revisions. They didn’t actually change any code.

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.

No. They add the below to wp-config.php:

define ('WP_POST_REVISIONS', 3);

Re: ACF Plugin no longer available on WordPress.org

#20

Post by didgeoridoo »

This is particularly bananas as ACF is basically table stakes for doing anything beyond blogging. I’d assume most websites that make actual money are thoroughly dependent on it.

To twist the knife on a personal spat, Mullenweg just blew up uncountable businesses on a double-holiday weekend. At this point, seriously, fuck that guy.

Post reply on HN