←back to thread

Secure Custom Fields by WordPress.org

(wordpress.org)
172 points ValentineC | 3 comments | 12 Oct 24 18:38 UTC | HN request time: 0.486s | source
Show context
RobotToaster ◴[12 Oct 24 19:15 UTC] No.41821624[source]▶
Wordpress banned forks from the plugin directory a while ago, so they're doing what they ban everyone else from doing. https://make.wordpress.org/plugins/2021/02/16/reminder-forke...
replies(2): >>41821877 #>>41821901 #
batuhanicoz ◴[12 Oct 24 19:47 UTC] No.41821901[source]▶
ACF isn’t a premium plugin (linked post only concerns those).

The linked post also might not reflect the current policies. This update was a security update and was done due to the unique circumstances around the original publisher.

replies(5): >>41821988 #>>41822021 #>>41822082 #>>41822182 #>>41822339 #
1. rasso ◴[12 Oct 24 20:37 UTC] No.41822339[source]▶
Exactly. ACF is free and open source. ACF Pro is not. Secure Custom Fields is based on the free version (ACF, without "Pro").
replies(2): >>41822847 #>>41825917 #
2. luckylion ◴[12 Oct 24 21:32 UTC] No.41822847[source]▶
It still uses trademarks from ACF, those are obviously not "open source", which also has been Matt's & wordpress.org's stance since forever: the _code_ is GPL, but the assets are not.

If you "fork" the assets, you're not covered by GPL.

Obviously it's nonsense to discriminate between the free version of a freemium plugin and a commercial plugin and this is simply a stupid way to lash out.

3. maxloh ◴[13 Oct 24 07:25 UTC] No.41825917[source]▶
Because WordPress is licensed under the GPL, all plugins must be licensed under GPL-compatible licenses. This applies to ACF Pro as well.