Most active commenters

    ←back to thread

    Secure Custom Fields by WordPress.org

    (wordpress.org)
    172 points ValentineC | 23 comments | 12 Oct 24 18:38 UTC | HN request time: 0.656s | source | bottom
    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 #
    1. 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 #
    2. jorams ◴[12 Oct 24 19:17 UTC] No.41821636[source]▶
    The pro version of the plugin is a separate install, this just rips out the upgrade notices.
    3. 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 #
    4. 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 #
    5. ◴[12 Oct 24 19:46 UTC] No.41821888{3}[source]▶
    6. sccxy ◴[12 Oct 24 19:50 UTC] No.41821922{3}[source]▶
    You are a disgrace to the open source community.

    I hope the lawsuit serves as a lesson to you.

    7. clessg ◴[12 Oct 24 19:54 UTC] No.41821956{3}[source]▶
    I'd normally never say something like this, but: seek therapy, man. Seriously. This is not normal. It will end badly for so many people, including yourself. It may not be too late.
    8. ◴[12 Oct 24 19:56 UTC] No.41821972{3}[source]▶
    9. NeonNautilus ◴[12 Oct 24 19:58 UTC] No.41821992{3}[source]▶
    I don't think punishing people for suing you typically plays well in court. Especially not if you, you know, publicly announce that's what you're doing.
    replies(1): >>41831140 #
    10. throw16180339 ◴[12 Oct 24 19:59 UTC] No.41821999{3}[source]▶
    There won't be a Wordpress community left if you continue as you have. What does the board think of your actions?
    11. maxbond ◴[12 Oct 24 20:11 UTC] No.41822103{3}[source]▶
    I've vouched this comment. I don't think we should be flagging this comment; it's not particularly out of line, and there's a significant interest in the community seeing Mullenweg's comments.
    12. Kye ◴[12 Oct 24 20:17 UTC] No.41822163{3}[source]▶
    Guy who started a fight tells target to stop hitting themselves
    13. wongogue ◴[12 Oct 24 20:31 UTC] No.41822291{3}[source]▶
    Please proceed, governor.
    14. skhr0680 ◴[12 Oct 24 20:42 UTC] No.41822380[source]▶
    AFAIK the free version never included “pro features” in the first place
    15. navigate8310 ◴[12 Oct 24 20:45 UTC] No.41822408{3}[source]▶
    What a 5 year old kid you are Matt. Good that the community can now see through it.
    16. Scaevolus ◴[12 Oct 24 20:53 UTC] No.41822464[source]▶
    So they forked some open source software and "hacked it up" to remove notices from the original creators? Fascinating.
    replies(1): >>41822753 #
    17. cyral ◴[12 Oct 24 21:21 UTC] No.41822753[source]▶
    Yup, removing post revisions which I think is single line change is hacking it up when WP Engine does it, but this is totally okay apparently.
    18. taikahessu ◴[12 Oct 24 21:25 UTC] No.41822781{3}[source]▶
    Business is war, I get it. But you chose to make innocent bystanders (your users) life difficult and you crossed a line by stealing code with an excuse that everyone sees through. This looks now more and more of a personal vendetta.
    19. mmsnowsniff ◴[12 Oct 24 21:27 UTC] No.41822801{3}[source]▶
    Can't wait for Matt to read this in a deposition. At this point, the dude seems to be intent on running up the highest tab possible.
    20. bombcar ◴[12 Oct 24 21:29 UTC] No.41822818{3}[source]▶
    These are clearly the actions of someone who is sure they'll win the lawsuit.

    (not)

    21. grodriguez100 ◴[12 Oct 24 22:38 UTC] No.41823343{3}[source]▶
    Trust is what has been broken.

    Childish.

    22. yard2010 ◴[13 Oct 24 07:54 UTC] No.41826042{3}[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?

    23. everforward ◴[13 Oct 24 20:10 UTC] No.41831140{4}[source]▶
    This was my reaction as well. This sounded like tortious interference before, but to blatantly announce that he’s trying to kill someone else’s business, for exercising their legal rights no less, sounds like a summary judgement waiting to happen.

    There is no dispute over the facts here if Matt is just going to announce his intents.

    I cannot imagine his rage when not only does WPE not have to pay him, but now he’s paying them.