Developers Remove Plugins From WordPress.org Repository After ACF Controversy

[Jyolsna]

[See the full post at: Developers Remove Plugins From WordPress.org Repository After ACF Controversy]

Loading…

[Stephen]

Ah, the exodus has begun. Not surprising really. No-one can feel sure that all their hard work will be safe if Matt suddenly decides he doesn’t approve of you.

Loading…

[Aaron Reimann]

I’m assuming that this is just the beginning.

Loading…

[Takis Bouyouris]

Refreshing to see that WPTavern is not enforcing the same tactics of suffocating contributors by blocking them, as the official WordPress dot org account is doing.

Loading…

[Ron]

This is getting wayyyy out of hand.

Is there no way that the self-proclaimed KING MM can be ousted from his .org role?

He’s already likely destroyed WP forever with his childishness but it’s worth a shot that those remaining can right the ship.

Loading…

[Fernando]

Dumb choice. Good luck to them.

Loading…

[Miroslav Glavic]

It wasn’t appropriation, it was more of a fork. That can happen under GPL.
Yes, the anti-Matt/WPE side is wrong. they harassed beyond belief a couple of the moderators of the Reddit WP sub.

No this is not the end of the world, no there is no exodus, yes those plugins (or any plugins) can be closed and moved off the W.

I will not renewing any licences with the plugins/companies mentioned above.

Loading…

[Joseph]

ACF and Pmpro are literally the worst plugins ever, ACF with its historically huge security flaws, and don’t even get me started on Pmpro, especially the PayPal extension. Dumping pmpro for woocommerce memberships was the best decision for my company. I fully concur.

Loading…

[Bastian]

Dude, seeing you try so hard to win Matt’s favor over all these years in the comments is just funny.

Loading…

[Ron]

Or pathetic?

Loading…

[J]

Matt has dug in so deep, he’d rather destroy WordPress than admit he’s wrong. This seems like a solid continuation of the beginning of the end.

Loading…

[Christian Zumbrunnen]

No, it’s not just a fork because then it would run under a new name. Actually it’s not better or even worse than what Matt is accusing WPEngine of.

It’s really, really sad.

Loading…

[Luke B]

You mean, a different name like “Secure Custom Forms”?

I am sure that what you specifically mean is that the WordPress.org would release it as a separate plugin alongside ACF, But if MM genuinely has an issue with some security flaw, that would still leave the unpatched version running in thousands of instances of wp.

Pulling plugins out of WordPress only ensures that people won’t use them at any level of volume as they have before.

Loading…

[Al]

As a developer as well as a web design house we believe that Automatic has the right to do what they want (legally) to protect their intellectual property.

I don’t see this as ‘the end’ because there really is nothing out there as ‘good’ or with such a large eco-system/community as WP.

I’ve read that a few people are talking about dropping WP. So where are they going to go? They are not going anywhere because there is no place to go!

Loading…

[Simon39]

As a developer, I will say that you have nowhere to go if you haven’t tried anything else.

Loading…

[alprado]

The only good thing about this whole mess is that WordPress has recognized the importance of Custom Fields. Without ACF, WordPress would barely function as a CMS.

Loading…

[Alan Stewart]

It wasn’t appropriation, but more of a fork, which is permissible under the GPL. Yes, the criticism of Matt and WPE is misguided, and unfortunately, a few moderators of the Reddit WordPress subreddit faced extreme harassment.

Loading…

[Ron]

The problem is that King Matt did it out of spite.

He is the cancer sucking the life out of WP right now.

MATT! Just go away….

Loading…

[Nancy Taylor]

It will be interesting to see how these actions shape the broader WordPress ecosystem moving forward.

Loading…

[WPSlash]

I hope that everything will be back to normal soon!

Loading…

[shaheen]

It will be intriguing to observe how these developments affect the larger WordPress ecosystem in the future.

Loading…

[Bezos]

This is an interesting development in the WordPress community! The removal of plugins after the ACF controversy really highlights the need for stringent quality control. It’s crucial for maintaining user trust and ensuring a secure environment. I hope this leads to clearer guidelines for developers moving forward. It would be great to see the community come together to improve standards and transparency. Looking forward to seeing how this evolves!

Loading…

[Stephen]

It wasn’t a fork Miroslav. Forking doesn’t involve actively blocking access to the original version and directing current users over to your fork. This was clearly spiteful appropriation.

Loading…

[Matthew]

I am not comfortable with hosting code on wordpress.org, however I also am not comfortable with the absolute fracturing of the plugin community.

Loading…

[jani87]

Several developers have removed their plugins from the WordPress.org repository following the controversy surrounding (ACF), as the incident raised concerns about plugin policies. This move reflects the growing frustrations over perceived unfair treatment and lack of transparency in plugin management.

Loading…

[Author]

Posts