3 ms·
Clearly AdvancedCustomFields should have filed a trademark to prohibit Wordpress from fully stealing it. GPL code, trademarked branding. If you want to fork th
by forrestthewoods 2y ago
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.
- ValentineC 2y ago> 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=US_APPLICATION&caseType=DEFAULT&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=98321164&caseSearchType=U... ACF — https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=US_APPLICATION&caseType=DEFAULT&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=U...
- forrestthewoods 2y agoOh nice. Then WordPress shouldn’t be able to take over without renaming, right?
- prettymuchnoone 2y agothey renamed to "secure custom fields"
- everforward 2y agoThey 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.