3 ms·
The fucked thing is that per the article, they're not even dedicating any resources to maintain it going forward, they've just made this one fix and are throwin
by Sebguer 2y ago
The fucked thing is that per the article, they're not even dedicating any resources to maintain it going forward, they've just made this one fix and are throwing it to other people to maintain if they want:
> Going forward, Secure Custom Fields is now a non-commercial plugin, and if any developers want to get involved in maintaining and improving it, please get in touch.
- photomatt 2y agoWe have taken on stewardship of this code going forward, and will dedicate engineers to it. Probably more than Silver Lake does.
- ceejayoz 2y agoSo, the ACF plugin is a useful contribution to the WordPress ecosystem? Significant enough to warrant bringing it in-house now? Is work on it included in your assessment of what WPE contributes?
- Sebguer 2y agoWhy don't you mention this in the post at all?
- deleted 2y ago[deleted]
- saaaaaam 2y agoYour shift of signifier here from WP Engine to Silver Lake is interesting. Clever tactic, private equity money is BAD! Unless it’s… I dunno? Black Rock p/e money?