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

91–100 of 151 posts

Re: ACF Plugin no longer available on WordPress.org

#91

Post by arielcostas »

sgdfhijfgsdfgds wrote: post #59
Cyberdog wrote: post #28

Earlier quoted context omitted.

How did the sites auto-update to have this plug-in removed/replaced? Are your sites set up to just automatically take push updates from WordPress central command or something and auto-modify themselves?!

Wordpress has a (highly effective) auto-updates mechanism for security patches. It was extended a couple of years ago to automatically apply plugin updates for you if you opted in, and I think automatic plugin updates may now be the default. (This is on balance a good thing; almost all WP vulnerabilities are outdated plugins, and until this mechanism was prevalent, WordPress occasionally had to live-patch existing in…

IDK if WordPress plugins respect SEMVER, but shouldn't this auto-update thingy update only patch versions, or minor versions at most? Idk, breaking changes like these is definitely not something you want your CMS to do overnight when you won't notice until you receive complaints that your site is broken

Re: ACF Plugin no longer available on WordPress.org

#92

Post by throw16180339 »

arielcostas wrote: post #88
throw16180339 wrote: post #78

Earlier quoted context omitted.

There isn't an actual difference. He uses both of them as he sees fit.

Wait, and the IRS is happy with all that? With an individual using company resources for what would appear to be "personal" activity outside the company? Same with the foundation?

He said that they're all his and he moves workers between them in a comment here. WP Engine mentions the tax exempt status of the foundation in their lawsuit.

Re: ACF Plugin no longer available on WordPress.org

#93

Post by sgdfhijfgsdfgds »

arielcostas wrote: post #91
sgdfhijfgsdfgds wrote: post #59

Earlier quoted context omitted.

Wordpress has a (highly effective) auto-updates mechanism for security patches. It was extended a couple of years ago to automatically apply plugin updates for you if you opted in, and I think automatic plugin updates may now be the default. (This is on balance a good thing; almost all WP vulnerabilities are outdated plugins, and until this mechanism was prevalent, WordPress occasionally had to live-patch existing in…

IDK if WordPress plugins respect SEMVER, but shouldn't this auto-update thingy update only patch versions, or minor versions at most? Idk, breaking changes like these is definitely not something you want your CMS to do overnight when you won't notice until you receive complaints that your site is broken

Yeah.

I don't know off-hand what the rule is for plugin updates, actually; I'd have to look it up.

As far as WordPress itself is concerned, the updater definitely does not auto-push updates to major WP versions by default [0], and they continue to patch older versions for a long time.

But at any rate, whether the plugin updates respect SEMVER or not, Matt/WP.org pushed this bullshit out as the most minor of minor version number changes over the previous ACF version: 6.3.6.2.

https://wordpress.org/plugins/advanced-custom-fields/advance... (scroll down to the bottom and you can download the previous version to diff it)

So as far as the poor benighted plugin updater is concerned, it's just a change to the display name, which is inconsequential.

[0] WP Engine do, ironically, on a pretty short timescale!

Re: ACF Plugin no longer available on WordPress.org

#94

Post by duskwuff »

jeltz wrote: post #36
chx wrote: post #32

Earlier quoted context omitted.

And very importantly: no one knows what that checkbox means and what are the consequences of checking it.

And Matt has refused to clarify when asked about it.

Including in the (rather common!) context of developers who maintain sites hosted on WPE.

Re: ACF Plugin no longer available on WordPress.org

#95

Post by maxbond »

LamaOfRuin wrote: post #89
maxbond wrote: post #58

Earlier quoted context omitted.

In hindsight this should've been all the warning anyone needed. In the future, when a BDFL telegraphs that they're willing to abuse their powers like this, we need to fork immediately. Open source is more important than any single project or any single BDFL. We can't allow open source to appear risky or unreliable relative to proprietary software, subject to the whims of volatile personalities. Open source is kind of…

Companies don't, as a rule, do this in software either. They make projects open source or contribute to open source projects because it's good for them . This is just as true in other industries. This is how every industry standard and protocol or similar works. It is beneficial to the participating companies and does not threaten them.

It's not that they don't benefit from collaborating, it's that they don't benefit as much as they could by demanding a royalty or licensing fee. Why shouldn't they? Everyone expects to be paid for their services. They're leaving money on the table for the benefit of the public at large.

Most of the "open" standards from other industries that I'm familiar with require a license, and certainly aren't open to participation by anyone and everyone. Let alone allowing you to modify and redistribute them.

But in software we've created a culture with different expectations. And I don't think we should take that for granted.

Re: ACF Plugin no longer available on WordPress.org

#96

Post by system2 »

mpol wrote: post #76
system2 wrote: post #62

Earlier quoted context omitted.

That's where the Sunday goes. I am trying to create an FTP script to mass update all wp-content plugins for this single package. It was on my mind but I was not expecting to have something bizarre happening from WordPress for one of the most crucial plugins in WordPress' existence.

Have you ever looked into wp-cli? It was made for this kind of task.

We use the wp-cli with cron jobs such as indexing when we post with API or database-related things. Even with wp-cli we must login to SSH individually. And this doesn't give us the wp-cli option since it is 3rd party zip file. We possibly can get the file, extract, and delete the old plugin with cli, and then enable the last updated plugin with with cli again with a script. Either way, we must create a script or suck it up, go into each wp individually, and take care of it from the backend...

Re: ACF Plugin no longer available on WordPress.org

#97

Post by system2 »

luckylion wrote: post #75
system2 wrote: post #64

Earlier quoted context omitted.

We use ACF with WP Code auto insert. ACF has prepend and append (in presentation tab) and this can be used to wrap the value with classes or other tags such as IDs, JS or others. When the ACF name changed, the prepend and append broke because prepend/append text showing must be configured in functions.php like this: add_filter('acf/format_value/name=mysnippet1', 'mysnippet1acf', 20, 3); function mysnippet1acf ($value…

Right, but why did that break? As far as I can tell that part hasn't been touched in the hostile takeover. https://plugins.trac.wordpress.org/browser/advanced-custom-f... It's still $this->add_field_filter( 'acf/format_value', array( $this, 'format_value' ), 10, 4 ); The file was last changed 7 weeks ago by deliciousbrains/wpengine and specifically the filter part is the same on their github.

Whatever they did, it didn't work. Maybe we are over-custimizing it but it is not unheard of to use ACF with multiple other plugins such as WP Code and custom scripts.

Re: ACF Plugin no longer available on WordPress.org

#98

Post by mikemitchelldev »

When the drama first started, I thought @photomatt’s plan might be to build ACF directly into WordPress (and maybe get rid of Gutenburg). I’m not sure if taking control of the plug-in is a step in that direction or if he probably could have incorporated ACF without taking over the plug-in. What’s the endgame?

Re: ACF Plugin no longer available on WordPress.org

#99

Post by batuhanicoz »

system2 wrote: post #97
luckylion wrote: post #75

Earlier quoted context omitted.

Right, but why did that break? As far as I can tell that part hasn't been touched in the hostile takeover. https://plugins.trac.wordpress.org/browser/advanced-custom-f... It's still $this->add_field_filter( 'acf/format_value', array( $this, 'format_value' ), 10, 4 ); The file was last changed 7 weeks ago by deliciousbrains/wpengine and specifically the filter part is the same on their github.

Whatever they did, it didn't work. Maybe we are over-custimizing it but it is not unheard of to use ACF with multiple other plugins such as WP Code and custom scripts.

The initial release of SCF only applied security fixes, changed the plugin name and removed upsells. I don't think there is any change that might cause the issue you are having.

If you can share the problem you are experiencing on Making WordPress Slack (#secure-custom-fields channel), I'm sure relevant people would love to help out ASAP.

I work at Automattic and I can get you in touch with people from WordPress.org if that's easier. You can email me at batuhan@a8c.com.

If there are any bugs, regressions or any issues with the fork, it's in the interest of everyone to quickly find and resolve them, so I'm sure your help would be appreciated.

Re: ACF Plugin no longer available on WordPress.org

#100

Post by mldevv »

system2 wrote: post #96
mpol wrote: post #76

Earlier quoted context omitted.

Have you ever looked into wp-cli? It was made for this kind of task.

We use the wp-cli with cron jobs such as indexing when we post with API or database-related things. Even with wp-cli we must login to SSH individually. And this doesn't give us the wp-cli option since it is 3rd party zip file. We possibly can get the file, extract, and delete the old plugin with cli, and then enable the last updated plugin with with cli again with a script. Either way, we must create a script or suck…

As an agency dev, this is the shit they don't think about. In my case, all that would have to be billed or go through pro-bono approval process.

"Just update it!" Until it all goes to shit, and we have to triage the whole mess.

Sorry you are dealing with this, I have spent the better part of the weekend trying to get them to understand this was inevitable.

Devs: "Don't deploy on Fridays" A8C/Matt: "We will deploy on SATURDAYS"

Post reply on HN