cf_custom-field meta import with checkbox custom fields

[daaath]

hello,

the plugin advanced custom fields gives you the option to create checkbox custom fields.

you can echo them for example with

<?php 
$field = get_field_object('custom-field-name');
$value = $field['value'];
$choices = $field['choices'];

if( $value ): ?>
<ul>
    <?php foreach( $value as $v ): ?>
    <li>
        <?php echo $choices[ $v ]; ?>
    </li>
    <?php endforeach; ?>
</ul>
<?php endif; ?>

if i take this checkbox customfield for the meta descript with %%cf_custom-field-name%% it only echos "Array" into the meta description.

Could you create a solution that the checked checkboxes are echoed with comma seperation ?

[Rarst]

I don't think that syntax can (or should) support more complicated data structures. If you want custom functionality like this you are better of using filters to implement it precisely, rather than us trying to come up with generic solution.

Makes sense? Have you tried looking into filters?

[daaath]

i have no idea. filters storage information in a function. but how to give it into the custom field that yoast can read?

[Rarst]

I would use wpseo_metadesc filter to do your modifications, based on data you want. User interface is just insufficiently flexible/convenient for more complex cases.

[daaath]

ok just tell me how to overwrite yoast meta with the wpseo meta on custom-post-types

[Rarst]

I am afraid that's getting into support territory and out of scope of the issue tracker. If you discover specific challenges with code being insufficiently flexible please feel free to report.

[daaath]

i found a better solution:
i make an string out of the array and put it in a new custom field which i insert into yoast seo

$check1 = implode(",", $value);
$check2 = (string)$check1;

check if it works:

echo $check2;
var_dump($check2); 

worked!

$postid1 = get_the_ID();
add_post_meta( $postid1 , 'v1', $check2 , true ); 

Problem: Yoast SEO still returns "Array"
i don´t get it.

[daaath]

i got it ... had to update database cause of array field "v1" . works fine now :-)