71–80 of 210 posts
https://github.com/sc0ttkclark/wordpress-fields-api
I'm not entirely sure what it is but it has over 350 stars and quite a few forks so it's probably important.
Earlier quoted context omitted.
This release fixes a separate security vulnerability from the original update.
The maintainers [1] and the Wordpress project’s core security team lead [2] said that the fix was already published, despite your blocking them from publishing it directly and irresponsibly disclosing the issue out of spite [3]. Was that not true? [1] https://x.com/wp_acf/status/1843376378210857441 [2] https://x.com/johnbillion/status/1843750679141331039 [3] https://x.com/johnbillion/status/1842627564453454049
Earlier quoted context omitted.
> Sherlocked The verb you're looking for is stole Sherloking is when a Walmart is built next to a cornershop. Here the dude tore open the corner shop while claiming to be a victim.
When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.
Isn't it here?
https://github.com/AdvancedCustomFields/acf
If you mean the licence, it's in readme.txt:
https://github.com/AdvancedCustomFields/acf/blob/master/read...
To that end, we reserve the following rights: ... to make changes to a plugin, without developer consent, in the interest of public safety.
Wordpress banned forks from the plugin directory a while ago, so they're doing what they ban everyone else from doing. https://make.wordpress.org/plugins/2021/02/16/reminder-forke...
ACF isn’t a premium plugin (linked post only concerns those). The linked post also might not reflect the current policies. This update was a security update and was done due to the unique circumstances around the original publisher.
Earlier quoted context omitted.
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.
We have taken on stewardship of this code going forward, and will dedicate engineers to it. Probably more than Silver Lake does.
Earlier quoted context omitted.
When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.
> When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF. Isn't it here? https://github.com/AdvancedCustomFields/acf If you mean the licence, it's in readme.txt: https://github.com/AdvancedCustomFields/acf/blob/master/read...
Earlier quoted context omitted.
When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF.
> When I posted, I was under the impression that ACF was open source. But the GitHub repo doesn’t list one, so if it’s not open source…WTF. Isn't it here? https://github.com/AdvancedCustomFields/acf If you mean the licence, it's in readme.txt: https://github.com/AdvancedCustomFields/acf/blob/master/read...
GPL code, trademarked branding. If you want to fork then you have to actually fork.
Oh the irony.