> it broke our snippets because we are using prepend and append texts to wrap our field values
Did they also rename filters and functions? I thought it was only the name and mentions of ACF in the docs. What did you rely on?
Did they also rename filters and functions? I thought it was only the name and mentions of ACF in the docs. What did you rely on?
add_filter('acf/format_value/name=mysnippet1', 'mysnippet1acf', 20, 3);
function mysnippet1acf ($value, $post_id, $field) {
if(!empty($value)){
$value = trim($field['prepend'].''.$value.''.$field['append']);
}else{
$value='';
}
return $value;
Long story short, if you are using ACF with advanced features, including logic and presentation, this hostile takeover breaks it.
Doesn't even matter if you use prepend/append for the fields, our logic-based ACF fields are also broken.
https://plugins.trac.wordpress.org/browser/advanced-custom-f...
It's still $this->add_field_filter( 'acf/format_value', array( $this, 'format_value' ), 10, 4 );
The file was last changed 7 weeks ago by deliciousbrains/wpengine and specifically the filter part is the same on their github.
If you can share the problem you are experiencing on Making WordPress Slack (#secure-custom-fields channel), I'm sure relevant people would love to help out ASAP.
I work at Automattic and I can get you in touch with people from WordPress.org if that's easier. You can email me at batuhan@a8c.com.
If there are any bugs, regressions or any issues with the fork, it's in the interest of everyone to quickly find and resolve them, so I'm sure your help would be appreciated.
If I were an employee of A8C I wouldn't be touching this code with a ten foot pole - employees can still be found guilty of criminal wrongdoing even if their employer told them to do something.