←back to thread

Secure Custom Fields by WordPress.org

(wordpress.org)
172 points ValentineC | 1 comments | 12 Oct 24 18:38 UTC | HN request time: 0s | 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 #
throw16180339 ◴[12 Oct 24 20:08 UTC] No.41822082[source]▶
There are a lot of other employers that won't make you lie for them.
replies(1): >>41822158 #
batuhanicoz ◴[12 Oct 24 20:16 UTC] No.41822158[source]▶
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.

replies(6): >>41822208 #>>41822219 #>>41822334 #>>41823101 #>>41825119 #>>41827872 #
1. throw16180339 ◴[12 Oct 24 20:36 UTC] No.41822334[source]▶
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.