71–80 of 151 posts
It is insane how Matt once again seem totally unable to understand the difference between Autoamattic and the WordPress Foudnation.
Concerning is not just the things he's said, but what he has done that go along with this. Self-dealing? Improper tax accounting?
After all this drama, it feels like WordPress has reached its peak and is now starting its decline. Of course, it will take years, and the process may be volatile, but the overall trend will likely be downward.
The only possibility I can think of is a fork.
This is particularly bananas as ACF is basically table stakes for doing anything beyond blogging. I’d assume most websites that make actual money are thoroughly dependent on it. To twist the knife on a personal spat, Mullenweg just blew up uncountable businesses on a double-holiday weekend. At this point, seriously, fuck that guy.
> This is particularly bananas as ACF is basically table stakes for doing anything beyond blogging. Not sure about this. I'd assume most Wordpress sites that make actual money are dependent on WooCommerce and Easy Digital Downloads, and maybe Gravity Forms/WP Forms for member subscriptions. None of these are reliant on ACF, and there's any number of WP plugins like this that do the whole job of some website niche or…
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…
This should be the top comment. It's already scary for a package manager to take control of a community package, even more so when sites auto-update to new code... but to break existing sites by completely changing the code that is provided in an auto-update is beyond the pale. Not a lawyer, but I imagine many consultancies will be talking to lawyers about this one; there are entire sections of law about interfering…
Earlier quoted context omitted.
> it broke our snippets because we are using prepend and append texts to wrap our field values Did they also rename filters and functions? I thought it was only the name and mentions of ACF in the docs. What did you rely on?
We use ACF with WP Code auto insert. ACF has prepend and append (in presentation tab) and this can be used to wrap the value with classes or other tags such as IDs, JS or others. When the ACF name changed, the prepend and append broke because prepend/append text showing must be configured in functions.php like this: add_filter('acf/format_value/name=mysnippet1', 'mysnippet1acf', 20, 3); function mysnippet1acf ($value…
https://plugins.trac.wordpress.org/browser/advanced-custom-f...
It's still $this->add_field_filter( 'acf/format_value', array( $this, 'format_value' ), 10, 4 );
The file was last changed 7 weeks ago by deliciousbrains/wpengine and specifically the filter part is the same on their github.
Earlier quoted context omitted.
Install the official free plugin from the advanced custom fields website and remove the SCF version. You won’t need to change any existing code then, and future updates will come from the plugin dev for ACF.
That's where the Sunday goes. I am trying to create an FTP script to mass update all wp-content plugins for this single package. It was on my mind but I was not expecting to have something bizarre happening from WordPress for one of the most crucial plugins in WordPress' existence.
Earlier quoted context omitted.
> This is particularly bananas as ACF is basically table stakes for doing anything beyond blogging. Not sure about this. I'd assume most Wordpress sites that make actual money are dependent on WooCommerce and Easy Digital Downloads, and maybe Gravity Forms/WP Forms for member subscriptions. None of these are reliant on ACF, and there's any number of WP plugins like this that do the whole job of some website niche or…
Fair enough. My info might be a little out of date from my web agency chop shop days, but I do recall that for essentially any substantial site it was assumed from day 1 that it would involve an ACF install. Probably integrated it into… fifty(?) websites over the years. I don’t recall the value prop of Pro, and I actually don’t think I ever touched it myself.
I don't think GP's distinction of "websites that make money" == "online stores" is accurate or meaningful. I use ACF on every website, my clients are money-making businesses. Only a couple of them are running WooCommerce (and those are running ACF as well).
Nothing about running a business on WordPress makes WooCommerce and ACF mutually exclusive.
It is insane how Matt once again seem totally unable to understand the difference between Autoamattic and the WordPress Foudnation.
Long time WordPress agency owner here. At the heart of this - if you consider it generously - is a principle that we can possibly all sign up to, namely that "large commercial entities" should (should from a moral, not legal standpoint) "pay back" to the open source software that makes them money. The principle however has been totally undermined by MM's actions, which have been completely out of line. His behaviour…
Now, when he's already failed to bring the community on board with his attacks, he decides that his next move is to make a big show of stealing something that had he done nothing many people would not have realized was a WP Engine property, with the net effect of reminding people that WP Engine has been responsible for maintaining what is widely considered to be the most essential plugin in the ecosystem.
But that doesn't count as giving back because... reasons.
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…