←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: 0.233s | source
Show context
stefanos82 ◴[12 Oct 24 18:46 UTC] No.41821399[source]▶
The URL though says "advanced-custom-fields"; Matt...I can't find the words to comment; I just shake my head -_-
replies(1): >>41821510 #
unsnap_biceps ◴[12 Oct 24 19:00 UTC] No.41821510[source]▶
If you look at the reviews, they took over the advanced-custom-fields plugin and modified the owner to be Wordpress.org and renamed it to Secure Custom Fields.

What a terrible look

They also modified it by ripping out the pro features, so if people update their ACF Plugin and they had pro features enabled, it'll just break their install

https://plugins.trac.wordpress.org/changeset/3167679/advance...

replies(4): >>41821636 #>>41821647 #>>41822380 #>>41822464 #
joe_hills ◴[12 Oct 24 19:17 UTC] No.41821647[source]▶
What a choice, and what poor timing.

Companies that make breaking changes on holiday weekends aren’t going to earn much goodwill from developers.

replies(1): >>41821870 #
photomatt ◴[12 Oct 24 19:44 UTC] No.41821870[source]▶
Nothing has broken. Perhaps WP Engine should have consider that before suing us.
replies(15): >>41821888 #>>41821922 #>>41821956 #>>41821972 #>>41821992 #>>41821999 #>>41822103 #>>41822163 #>>41822291 #>>41822408 #>>41822781 #>>41822801 #>>41822818 #>>41823343 #>>41826042 #
1. yard2010 ◴[13 Oct 24 07:54 UTC] No.41826042[source]▶
There must be a timeline in which this is de-escalated, compromises are being made and everyone's happy.

In your perspective - what does it look like? What could be done to go the opposite way and keep going?

Also, I'm surprised to see people only siding with WP Engine here. Usually the discussions here are much more balanced.. What do you think could be the reason for it?