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

121–130 of 151 posts

Re: ACF Plugin no longer available on WordPress.org

#121

Post by oceanstone »

photomatt wrote: post #109
n3storm wrote: post #33

Earlier quoted context omitted.

pass the bill to matt when you finish fixing those broken wp.

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 est…

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.

Re: ACF Plugin no longer available on WordPress.org

#122

Post by hadad »

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…

PLugin theft FAFO moment, doing bad QAs, what a joke

Re: ACF Plugin no longer available on WordPress.org

#123

Post by djprmf »

oceanstone wrote: post #121
photomatt wrote: post #109

Earlier quoted context omitted.

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 est…

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.

[flagged]

Re: ACF Plugin no longer available on WordPress.org

#124

Post by oceanstone »

djprmf wrote: post #123
oceanstone wrote: post #121

Earlier quoted context omitted.

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.

[flagged]

Hi account with no other comments, no submissions, and no favorites, after registering 5+ years ago

Re: ACF Plugin no longer available on WordPress.org

#125

Post by ChocolateGod »

sangnoir wrote: post #112
arielcostas wrote: post #87

Earlier quoted context omitted.

Creating an open registry would be nice, or even for developers to be able to host their own repos for others to install plugins from (à la Linux package managers), to avoid such centralisation. Ideally, those repos would be hosted by each party, and then hosting providers would be able to host their own mirrors containing many packages for all the installs, giving a similar experience to what is now offered by Mr. M…

> Creating an open registry would be nice, or even for developers to be able to host their own repos for others to install plugins from (à la Linux package managers), to avoid such centralisation. The security trade offs for this would not be worth it, IMO, considering WPs auto-updating features.

One could create a registry that uses PSK similar to mobile applications so a install only auto accepts an updated package if it's signed by the author.

Would prevent the issue above.

Re: ACF Plugin no longer available on WordPress.org

#127

Post by ryoshu »

sgdfhijfgsdfgds wrote: post #55
didgeoridoo wrote: post #20

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.

> This is particularly bananas as ACF is basically table stakes for doing anything beyond blogging. Not sure about this. I'd assume most Wordpress sites that make actual money are dependent on WooCommerce and Easy Digital Downloads, and maybe Gravity Forms/WP Forms for member subscriptions. None of these are reliant on ACF, and there's any number of WP plugins like this that do the whole job of some website niche or…

There are plenty of uses for WordPress for marcom sites for Fortune 500 brands that don't use those sites for transactional revenue, but they serve millions of impressions a month that rely on ACF. This is a supply chain attack. The security discussions with client IT groups happening this week are going to be a much bigger deal than they were last week.

The erratic and bizarre behavior of the BDFL that runs WordPress and Automattic has proven himself untrustworthy and is causing massive damage to the WordPress ecosystem.

Re: ACF Plugin no longer available on WordPress.org

#128

Post by nailer »

dmje wrote: post #46

Long time WordPress agency owner here. At the heart of this - if you consider it generously - is a principle that we can possibly all sign up to, namely that "large commercial entities" should (should from a moral, not legal standpoint) "pay back" to the open source software that makes them money. The principle however has been totally undermined by MM's actions, which have been completely out of line. His behaviour…

A reasonable standard for the plugin infrastructure would be to charge and allow free access to people with sufficient contribution history.

So Matt’s company which has sufficient contribution history would get free access and WP engine could either pay for access, contribute more to WordPress, or make their own plug-in infrastructure.

Re: ACF Plugin no longer available on WordPress.org

#129

Post by CodeWriter23 »

GenerocUsername wrote: post #35
wmf wrote: post #31

Earlier quoted context omitted.

They replaced ACF with a forked version so the functionality is still there. That doesn't excuse it but the situation is not so dire for users.

Asking for a friend... What's the migration path to a different plugin look like? Seamless? Better be duckin seamless

Tell your friend to get ready to jump to the next thing.

Re: ACF Plugin no longer available on WordPress.org

#130

Post by CodeWriter23 »

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.

You're out here on HN acting completely unfamiliar with the idea of configuring to limit resource consumption?
Post reply on HN