Re:Secure Custom Fields by WordPress.org
by joe_hills on Saturday October 12, 2024 @03:17PM
(#41821647)
What a choice, and what poor timing.
Companies that make breaking changes on holiday weekends aren’t going to earn much goodwill from developers.
Re:Secure Custom Fields by WordPress.org
by photomatt on Saturday October 12, 2024 @03:44PM
(#41821870)
Nothing has broken. Perhaps WP Engine should have consider that before suing us.
Re:Secure Custom Fields by WordPress.org
by clessg on Saturday October 12, 2024 @03:54PM
(#41821956)
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.
Guy who started a fight tells target to stop hitting themselves
Re:Secure Custom Fields by WordPress.org
by maxbond on Saturday October 12, 2024 @04:11PM
(#41822103)
[delayed]
Re:Secure Custom Fields by WordPress.org
by throw16180339 on Saturday October 12, 2024 @03:59PM
(#41821999)
There won't be a Wordpress community left if you continue as you have. What does the board think of your actions?
You are a disgrace to the open source community.
I hope the lawsuit serves as a lesson to you.
Re:Secure Custom Fields by WordPress.org
by NeonNautilus on Saturday October 12, 2024 @03:58PM
(#41821992)
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.
Re:Secure Custom Fields by WordPress.org
by everforward on Sunday October 13, 2024 @04:10PM
(#41831140)
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.
Re:Secure Custom Fields by WordPress.org
by wongogue on Saturday October 12, 2024 @04:31PM
(#41822291)
Please proceed, governor.
Re:Secure Custom Fields by WordPress.org
by navigate8310 on Saturday October 12, 2024 @04:45PM
(#41822408)
What a 5 year old kid you are Matt. Good that the community can now see through it.
Re:Secure Custom Fields by WordPress.org
by taikahessu on Saturday October 12, 2024 @05:25PM
(#41822781)
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.
Re:Secure Custom Fields by WordPress.org
by mmsnowsniff on Saturday October 12, 2024 @05:27PM
(#41822801)
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.
Re:Secure Custom Fields by WordPress.org
by bombcar on Saturday October 12, 2024 @05:29PM
(#41822818)
These are clearly the actions of someone who is sure they'll win the lawsuit.
(not)
Re:Secure Custom Fields by WordPress.org
by grodriguez100 on Saturday October 12, 2024 @06:38PM
(#41823343)
Trust is what has been broken.
Childish.
Re:Secure Custom Fields by WordPress.org
by yard2010 on Sunday October 13, 2024 @03:54AM
(#41826042)
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?
Re:Secure Custom Fields by WordPress.org
by jorams on Saturday October 12, 2024 @03:17PM
(#41821636)
The pro version of the plugin is a separate install, this just rips out the upgrade notices.
Re:Secure Custom Fields by WordPress.org
by skhr0680 on Saturday October 12, 2024 @04:42PM
(#41822380)
AFAIK the free version never included “pro features” in the first place
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...