Secure Custom Fields by WordPress.org • Hacker News Board

Re: Secure Custom Fields by WordPress.org

#51

Post by batuhanicoz » Sat, Oct 12, 2024, 7:47 PM UTC

RobotToaster wrote: post #7

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...

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.

Re: Secure Custom Fields by WordPress.org

#52

Post by sureIy » Sat, Oct 12, 2024, 7:48 PM UTC

This gets better by the day.

I'm so rooting for WPE and I hope the judge will lay it heavy.

Re: Secure Custom Fields by WordPress.org

#53

Post by bullenweg » Sat, Oct 12, 2024, 7:48 PM UTC

photomatt wrote: post #41

ivanmontillam wrote: post #24

Earlier quoted context omitted.

This is excellent! Is there a repo of this website? It would be good to have for preservation purposes.

It actually is an excellent website, and the repo is here: https://github.com/bullenweg/bullenweg.github.io

I have been unable to convince Jason Bahl to share the ~threats~ ~coercion~ terms you used to convince him to join Automattic. Your contribution via GitHub of the terms that you used to ~coerce~ persuade him into defecting would be appreciated.

Re: Secure Custom Fields by WordPress.org

#54

Post by sccxy » Sat, Oct 12, 2024, 7:50 PM UTC

photomatt wrote: post #44

joe_hills wrote: post #11

Earlier quoted context omitted.

What a choice, and what poor timing. Companies that make breaking changes on holiday weekends aren’t going to earn much goodwill from developers.

Nothing has broken. Perhaps WP Engine should have consider that before suing us.

[flagged]

Re: Secure Custom Fields by WordPress.org

#55

Post by martin_a » Sat, Oct 12, 2024, 7:51 PM UTC

Just stealing plugins right now? Or is this some kind of "eye for an eye" situation?

I'm really turned down from the whole ecosystem by this total shitshow. Seems like everything could be pulled from under running sites if some clown decides he doesn't like it anymore.

At this point I just hope that WP Engine wins whatever lawsuit happens and Matt Mullenweg (and everybody who was involved besides him) has to pack his things and leave everything WP-related forever.

Re: Secure Custom Fields by WordPress.org

#56

Post by _cenw » Sat, Oct 12, 2024, 7:51 PM UTC

I thought there weren't any hinges left for Matt to unhinge. He dug for that minior vulnerability to be to able to justify that takeover.

Who can ever trust this guy and his company, ever again?

Re: Secure Custom Fields by WordPress.org

#57

Post by delichon » Sat, Oct 12, 2024, 7:52 PM UTC

DonnieBurger wrote: post #33

delichon wrote: post #18

As a builder of a small specialized CMS for which WordPress is a large generalized competitor, thanks Matt. Refugees welcome.

I'm interested. Please do share.

Thanks but I'm going for pseudonymity on this account. Just a few dozen clients.

Re: Secure Custom Fields by WordPress.org

#58

Post by ceejayoz » Sat, Oct 12, 2024, 7:53 PM UTC

photomatt wrote: post #43

Sebguer wrote: post #30

Earlier quoted context omitted.

The fucked thing is that per the article, they're not even dedicating any resources to maintain it going forward, they've just made this one fix and are throwing it to other people to maintain if they want: > Going forward, Secure Custom Fields is now a non-commercial plugin, and if any developers want to get involved in maintaining and improving it, please get in touch.

We have taken on stewardship of this code going forward, and will dedicate engineers to it. Probably more than Silver Lake does.

So, the ACF plugin is a useful contribution to the WordPress ecosystem? Significant enough to warrant bringing it in-house now? Is work on it included in your assessment of what WPE contributes?

Re: Secure Custom Fields by WordPress.org

#59

Post by clessg » Sat, Oct 12, 2024, 7:54 PM UTC

photomatt wrote: post #44

joe_hills wrote: post #11

Earlier quoted context omitted.

What a choice, and what poor timing. Companies that make breaking changes on holiday weekends aren’t going to earn much goodwill from developers.

Nothing has broken. Perhaps WP Engine should have consider that before suing us.

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.

Re: Secure Custom Fields by WordPress.org

#60

Post by martin_a » Sat, Oct 12, 2024, 7:55 PM UTC

butz wrote: post #50

I wonder what will happen to old websites I built with ACF and did not touch for years? Are they vulnerable now, as owners cannot get updates for ACF?

I had to login to several sites and make sure that the plugins would not auto-update. This is pretty much like a rogue actor taking over a plugin.