5 ms·
> replaced it with another plugin that broke people's websites What makes you think it broke someone’s website? AFAIK they just patched the security issue that
by usaphp 2y ago
> replaced it with another plugin that broke people's websites
What makes you think it broke someone’s website? AFAIK they just patched the security issue that wp engine team couldn’t patch because they were locked out from pushing to repo?
- bad_user 2y agoFirstly, the security patch was already published by the ACF team, and that wasn't the code that was pushed. This was a package takeover, slug, reviews, users, everything: https://www.advancedcustomfields.com/blog/acf-plugin-no-longer-available-on-wordpress-org/ https://www.advancedcustomfields.com/blog/acf-plugin-no-long... People woke up to their website being updated to “Secure Custom Fields”, an alternative (or a fork) that's not fully compatible. Here's one such report from HN: https://news.ycombinator.com/item?id=41830709 https://news.ycombinator.com/item?id=41830709
- danieljacksonno 2y agoThey turned off all pro features
- skhr0680 2y agoWhat Wordpress did is insane, but let’s not spread misinformation. There were no pro features in the free plugin to turn off, they removed advertising for the pro version.