Thomas Kr?ftner

With that limited info it is really hard to debug but my first guesses would be some other code messing with the queries. I see that you are using some heavy plugins like Jetpack and Elementor on that site, where especially the latter is messing a lot with the WP internals.
Also it seems you are using a Redis Cache which might be messing with the transients and cause a version of the issue hinted at above.

I guess to be able to properly debug this disable Redis and all plugins. Check if the issues goes away and if yes then re-enable them one by one to see when it reappears.

Thanks, 5.0.1 fixed this!

Thanks for the added details. I can now see why this isn’t working for you: As stated in the plugin description the addons for ACF 4 aren’t supported. So you’ll need to update to ACF 5 to be able to use any Pro Features like Repeaters. Especially now with the imminent release of ACF 5 Free we’ll not be putting further effort into extending support for ACF 4, sorry.

Thanks for your patience. I am still having a hard time reproducing this. Could you check to see if there are any JavaScript errors? Here is some help on how to check that: https://kb.yoast.com/kb/how-to-find-javascript-errors-with-your-browsers-console/

Also probably a duplicate of https://www.ads-software.com/support/topic/wysiwyg-fields-being-ignored/

Thanks for reporting and your patience. I am having a hard time reproducing the issue, could you please both add some more information about your setup?

WordPress version:
ACF Content Analysis for Yoast SEO version:
Yoast SEO version:
ACF type: free/pro
ACF version:
Relevant plugins:

Thanks for all your patience. Could it be that you have manually set the select2 version from 4 to 3 as explained here https://www.advancedcustomfields.com/blog/acf-pro-5-6-0-ui-ux/ (scroll down a bit)?

If yes then this is a known problem and we already have a fix ready to be released with the next version. As a workaround you can change Select2 back to v4 (the default in ACF 5.6+) as explained above.

If this isn’t it please let us know so we can investigate further what the issue is.

As I had the same issue I looked at the code and it seems as this is easy to fix. It boils down to removing the validation for the “radio” field like this:

remove_filter( 'wpcf7_validate_radio', 'wpcf7_checkbox_validation_filter', 10 );

Be aware that this globally disables validation for “radio”. I don’t see any side-effects right now but be aware what you are doing here.

For anyone wanting to dig deeper, this is the relevant change in 4.9: https://plugins.trac.www.ads-software.com/browser/contact-form-7/tags/4.9/modules/checkbox.php#L206

• This reply was modified 7 years ago by Thomas Kr?ftner.

Duplicate of https://www.ads-software.com/support/topic/how-to-disable-or-fix-the-new-feature-of-radio-buttons/

Okay, thanks for the screenshot, that seems to be something new. We’ll look into it.

Thanks for reporting. Are you sure you have the most current version 2.0.1 installed? We had that issue before with 2.0.0 but that should be resolved in 2.0.1.

In case you are on 2.0.1. – can you check if you see any JS errors? Here is a link if you don’t know how to find that out: https://kb.yoast.com/kb/how-to-find-javascript-errors-with-your-browsers-console/

I’m glad this helped. I just wanted to reiterate that this effectively disables the analysis of images and gallery fields but as a temporary workaround it should be fine.

I have also created an issue in github for further investigation in case you want to follow that as well: https://github.com/Yoast/yoast-acf-analysis/issues/120

Okay, strange. I can’t reproduce this right now but we have the issue on our bug tracker so at some point we’ll look into it and report back here.

Thanks for reporting and all the detailed information. I just have some more. ?? Do you have Image and/or Gallery fields added to the page?

I haven’t tracked this down yet but I suspect that it is related to the scrapers for those fields. Could you try disabling the support for those fields and see if the issue goes away?

add_filter( 'yoast-acf-analysis/blacklist_type', function ( $blacklist_type ) {
    $blacklist_type->add( 'image' );
    $blacklist_type->add( 'gallery' );
    return $blacklist_type; 
});

Sorry if I wasn’t clear enough. Let me try again:

1. Create a new, empty category term so that Yoast says “0 words”
2. Add 1 word to the ACF field. Yoast will still show “0 words”
3. Add 1 word to the default field. Yoast should now show “2 words”.

So to summarize the issue is that Yoast does include the ACF field, it just doesn’t trigger an update of the word count when you edit the ACF field. So you need to make any change to the default field to trigger an update. I hope this is clearer now.

Any how I have also created an issue over at Github for what I was able to reproduce, I just wanted to make sure we’re talking about the same thing. Here is the link to the issue in case you want to follow that as well, but I’ll keep you update here in any case.
https://github.com/Yoast/yoast-acf-analysis/issues/118