Live data from Hacker News

Secure Custom Fields by WordPress.org

wordpress.org

91–100 of 210 posts

Re: Secure Custom Fields by WordPress.org

#91
post #25

Pathetic. Matt banned one of the most popular WordPress plugins. Then, he forked the code and hosted it on WP.org, which is against the Terms of Service. He also hosted it in the plugin directory on the same path as ACF, stealing its SEO traffic. Wow! Matt's state of mind is clearly not good. If I were an investor in WordPress, I would start thinking about cutting my losses. WordPress will not recover from this self-…

Have you read the GPL?

Parent does not mention GPL, nor is this a GPL issue. It's about the takeover of an existing plugin and it's reviews/installs.

Re: Secure Custom Fields by WordPress.org

#92
post #25

Pathetic. Matt banned one of the most popular WordPress plugins. Then, he forked the code and hosted it on WP.org, which is against the Terms of Service. He also hosted it in the plugin directory on the same path as ACF, stealing its SEO traffic. Wow! Matt's state of mind is clearly not good. If I were an investor in WordPress, I would start thinking about cutting my losses. WordPress will not recover from this self-…

Have you read the GPL?

[deleted]

Re: Secure Custom Fields by WordPress.org

#94
post #8

We no longer do custom WordPress work --- it turned out to never be worth the hassle --- but when we did, our company used ACF extensively. High quality plugin with responsive support and very fair licensing terms. This --- to me --- smacks of complete bullshit.

It is complete bullshit, but calling ACF high quality is also pretty out there. It's one of those giants in WP that is stuck in the past, arguably much like a lot of core.

To be fair we haven’t worked with WP in 4 years; our experience with ACF was always positive.

Re: Secure Custom Fields by WordPress.org

#95
post #45

Earlier quoted context omitted.

> Sherlocked The verb you're looking for is stole Sherloking is when a Walmart is built next to a cornershop. Here the dude tore open the corner shop while claiming to be a victim.

When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.

I think being GPL is a requirement to host plugins in wp.org, so yes, that free version available there is (was?) open source.

Re: Secure Custom Fields by WordPress.org

#96
post #25

Pathetic. Matt banned one of the most popular WordPress plugins. Then, he forked the code and hosted it on WP.org, which is against the Terms of Service. He also hosted it in the plugin directory on the same path as ACF, stealing its SEO traffic. Wow! Matt's state of mind is clearly not good. If I were an investor in WordPress, I would start thinking about cutting my losses. WordPress will not recover from this self-…

Have you read the GPL?

[flagged]

Re: Secure Custom Fields by WordPress.org

#97

Earlier quoted context omitted.

What a choice, and what poor timing. Companies that make breaking changes on holiday weekends aren’t going to earn much goodwill from developers.

Nothing has broken. Perhaps WP Engine should have consider that before suing us.

Please proceed, governor.

Re: Secure Custom Fields by WordPress.org

#98
post #45

Earlier quoted context omitted.

> Sherlocked The verb you're looking for is stole Sherloking is when a Walmart is built next to a cornershop. Here the dude tore open the corner shop while claiming to be a victim.

When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.

Forking isn't the issue. Here they just took the whole ID/address from which existing installations will continue to be updated from. This is theft. I have no doubt it will be added to the lawsuit.

While technically they own the platform and can do whatever they want, there is clearly ill intent here and it'll be used against them.

Re: Secure Custom Fields by WordPress.org

#99
post #71

Related: the main developer on the Fields API proposal is calling it quits on involvement with WordPress. https://github.com/sc0ttkclark/wordpress-fields-api I'm not entirely sure what it is but it has over 350 stars and quite a few forks so it's probably important.

Now resigned maintainer Scott is also lead dev of Pods, awesome ACF-like plugin.

Lines have been crossed when stealing other people's code, what happened in the case of ACF to SCF, IMHO.

Re: Secure Custom Fields by WordPress.org

#100

Earlier quoted context omitted.

There are a lot of other employers that won't make you lie for them.

If you point to any lies told by me, I would love to correct them. No one has told me to come here and defend anyone. I work at a part of Automattic that is isolated from anything WordPress — I don’t have to be here. I am defending values I believe in. I am trying to make sure correct information is out there. You are free to not believe that of course.

The correct information is that your employer created the security problem as part of their shakedown attempt. They then banned the WP Engine developers from Wordpress so that they couldn't update the plugin. Now they've forked the plugin, removed the commercial upgrade, and renamed it.

I'm not sure where values come into it. I'd be ashamed to work there.

Post reply on HN