Live data from Hacker News

ACF Plugin no longer available on WordPress.org

advancedcustomfields.com

1–10 of 151 posts

Re: ACF Plugin no longer available on WordPress.org

#3
Wow, this is a big deal. Matt Mullenweg taking over ACF like that? Not cool. It's not just about messing with years of hard work, but think about all those WordPress sites now running code the ACF team didn't approve. Kinda scary when you think about it. Hope this doesn't become a trend in the open-source world.

Re: ACF Plugin no longer available on WordPress.org

#8

Wow, this is a big deal. Matt Mullenweg taking over ACF like that? Not cool. It's not just about messing with years of hard work, but think about all those WordPress sites now running code the ACF team didn't approve. Kinda scary when you think about it. Hope this doesn't become a trend in the open-source world.

It needs to stop here.

Re: ACF Plugin no longer available on WordPress.org

#9
Oh god, this gave me a minor heart attack. We are using over 20 ACF fields for 150+ sites. I thought it was completely out of the WordPress ecosystem. I am glad they have the zip download and continuing auto updates.

EDIT: I confirm our ACF plugins on sites are all switched to secure custom fields. This is so shady, it broke our snippets because we are using prepend and append texts to wrap our field values. Now they are all broken and we have to update all our sites (also our client's sites). Let's see what comes next...

EDIT2: There goes my Sunday. I received our first ticket regarding broken homepage widgets. I have to sit down and update every site one by one. Thank you Matt Mullenweg for ruining my Sunday plans.

Re: ACF Plugin no longer available on WordPress.org

#10

Hang on, the ACF plugin has been replaced by a different plugin, published by a different party? And install on every Wordpress installation?!?

The whole thing is https://plugins.trac.wordpress.org/changeset/3167679/advance... it's very close to functionality wise right now to ACF. Not identical, already. While I am not a lawyer it almost certainly violates the ACF trademark as the code and reviews contains a lot of reference to ACF and the Advanced Custom Fields trademark which is literally the project slug. Some suspect a request for emergency injunction might follow next week. And most certainly it also violates community trust very, very big time.

This on top of the "swear fealty" checkbox on login which caused multiple high profile contributors to leave and now shut the accessibility team down https://i.imgur.com/0jCZnlm.png

Post reply on HN