mldevv

5 ms·

1.
by mldevv 2y ago
Its been almost a week, what correction would you like to make to this? You've been dodging and the community deserves honest answers.
2.
by mldevv 2y ago
Yes and that is a huge deal - I made this point to others that it shouldn't be considered a minor version change
3.
by mldevv 2y ago
As an agency dev, this is the shit they don't think about. In my case, all that would have to be billed or go through pro-bono approval process. "Just update it!" Until it all goes to shit, and we have to triage the whole mes
4.
by mldevv 2y ago
I agree with this take, professionally. People have generally saw their investment as a positive, whether its deemed "enough" or not
5.
by mldevv 2y ago
My opinion as well as many as my peers is that ACF could have been rolled into core or bought by Matt long long before it was acquired by WPE, which most of us found as a good thing, being that its a critical plugin and gained long term sup
6.
by mldevv 2y ago
They use the parts of wordpress that are specifically built in to make modifications, as any other site maintainer would hosting their own install. You are mistaken.
7.
by mldevv 2y ago
WP and/or A8C took over the existing plugin, so that sites that have auto-update on were automatically bumped to the SCF version instead of the historical ACF which obviously had a different team of maintainers
8.
by mldevv 2y ago
(community member, not affiliated with WP, WPE, or A8C) I can confirm this has been escalated internally in the WP slack. I can also provide this context which I found concerning, given the way this was taken over and rolled out on a Saturd