[ad_1]
[ad_2]
Especially considering all the drama, wondering if I should just stay away from anything WPengine related, in case Matt goes totally ballistic?
Especially considering all the drama, wondering if I should just stay away from anything WPengine related, in case Matt goes totally ballistic?
That’s what I was thinking.
Anything new using ACF is going to be updated directly by WPEngine, even for the free version (as long as you don’t download it from .org).
I think the risk to ACF-specifically is pretty low.
I wouldn’t be hosting new sites on WPE OR anything Matt owns for now though.
ACF
Not Pods. We inherited a site using it and it was a database monster.
Carbon Fields.
Both are great!
On the one hand, ACF Pro is powerful and in combination with ACF Extended you can have endless possibilities, especially if you don’t want to code yourself. However, both of them are paid plugins. However, you can still go with the free ACF, but it is less powerful compared to PODS.
On the other, If you are not afraid of coding and extending existing capabilities in Pods using custom coding and PODS templates, go for Pods!
ACF is by far the best choice option/functionality wise, and I use it, but it’s gated now by a subscription.
Before WPE you could use an unactivated version of ACF PRO, now you can’t.
Which makes it a piece of sht plugin now.
If the subscription ends, I can’t create new pro fields in my current version, which again, makes it garbage.
As soon as a native solution gets baked in WordPress I’m jumping ship… like everyone else will probably.
We love ACF. Would be cool to see something like it in core too. WPE recently published an article on how to update ACF, then you’ll be able to do updates as usual once you do that.
Not Pods. Haven’t tried ACPT, maybe look at
CubeWP. The free version has lots of features
Why not Toolset?
ACF is better, especially if you set up the data serialization and mapping: https://github.com/TwistedAndy/wp-theme/blob/cef28826f38fb136522bd88fb92197373cd42fdb/theme/includes/theme/acf.php
It will dramatically decrease the number of metadata required. Also, it will be possible to use the default Metadata API with complex fields like repeaters, groups, and flexible content.
There is no drama. The ACF “issue” has been solved.
Tried Pods on a client site, but one of the updates broke a bunch of functionality on the site, so I ran back to ACF and haven’t used Pods since.
Pods was simpler to use when integrating custom fields in a block, but I just don’t trust it anymore.
I have a lifetime license with ACF and is definitely the best tool so I will use ACF
There won’t be any issues with ACF now they’re handling the updates themselves, I say use them to support the team there.
To be honest, considering Matt can mess with any plugin on the repo, it’s much safer to deal with the maker of a plugin directly, it’s in their own interest to keep their plugin running well.
Matt already went ballistic. ACF.