News for hackers. Stuff that matters.
Re:Secure Custom Fields by WordPress.org by CharlesW on Saturday October 12, 2024 @03:56PM (#41821973)
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.
Re:Secure Custom Fields by WordPress.org by ValentineC on Saturday October 12, 2024 @04:02PM (#41822031)
> 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.

Isn't it here?

https://github.com/AdvancedCustomFields/acf

If you mean the licence, it's in readme.txt:

https://github.com/AdvancedCustomFields/acf/blob/master/read...

Re:Secure Custom Fields by WordPress.org by CharlesW on Saturday October 12, 2024 @04:10PM (#41822094)
Thanks! The GitHub app reports it as "None" (https://imgur.com/a/5dyaTfX), but now I see it's "GPLv2 or later".
Re:Secure Custom Fields by WordPress.org by forrestthewoods on Saturday October 12, 2024 @04:10PM (#41822095)
Clearly AdvancedCustomFields should have filed a trademark to prohibit Wordpress from fully stealing it.

GPL code, trademarked branding. If you want to fork then you have to actually fork.

Oh the irony.

Re:Secure Custom Fields by WordPress.org by ValentineC on Saturday October 12, 2024 @04:17PM (#41822159)
> Clearly AdvancedCustomFields should have filed a trademark to prohibit Wordpress from fully stealing it.

They did:

Advanced Custom Fields — https://tsdr.uspto.gov/#caseNumber=98321164&caseSearchType=U...

ACF — https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=U...

Re:Secure Custom Fields by WordPress.org by forrestthewoods on Saturday October 12, 2024 @07:20PM (#41823617)
Oh nice. Then WordPress shouldn’t be able to take over without renaming, right?
Re:Secure Custom Fields by WordPress.org by prettymuchnoone on Sunday October 13, 2024 @01:56AM (#41825544)
they renamed to "secure custom fields"
Re:Secure Custom Fields by WordPress.org by everforward on Sunday October 13, 2024 @03:48PM (#41830955)
They kept the permalink afaik, which is probably still likely to cause confusion in the marketplace and may still be a trademark issue.

Without knowing this drama, if I found and clicked an ACF link on a 2 year old Reddit post and ended up at Secure Custom Fields, I’m not sure I’d know it wasn’t by the ACF folks. Just their branding for the v2 or whatever. I think customers have a reasonable expectation that permalinks won’t take them to unrelated products.

Re:Secure Custom Fields by WordPress.org by mthoms on Sunday October 13, 2024 @04:59PM (#41831541)
Yep. And the string 'acf' is used throughout the plugin and the plugin download page (in reviews, etc). And 'acf' is indeed a pending trademark registration.

Not good.

Re:Secure Custom Fields by WordPress.org by saaaaaam on Friday October 18, 2024 @06:07PM (#41883933)
Very much doubt they will be able to trademark “acf”.
Re:Secure Custom Fields by WordPress.org by danillonunes on Saturday October 12, 2024 @04:28PM (#41822266)
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 by sureIy on Saturday October 12, 2024 @04:33PM (#41822313)
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.