markyz89

Actually, this was due to a modification a colleague implemented in our theme, so nothing to do with WPBakery.

You can consider the initial post redundant and ignore, there is no problem with the plugin.

Hi @tacoverdo, thanks for getting back to me.

I can’t really give you a lot more detail. This problem (that content in custom fields wasn’t being analysed by Yoast) was reported to me as the developer for our organisation by one of our departments who had their site built externally. I was going to install your plugin as a solution but then saw it was already installed. I can’t see any evidence of this plugin doing anything, so there’s not really anything to take a screenshot of, but I’ve been told it was working before.

The timeline matched up with a Yoast update so I suggested in this question that might have been the reason for this issue.

Our debug log has the following error:
[05-Oct-2021 14:40:15 UTC] PHP Notice: Trying to get property ‘post_type’ of non-object in /kunden/328878_10247/webseiten/provegincubator.com10082021/wp-content/plugins/wordpress-seo/src/integrations/third-party/elementor.php on line 156

So that suggests there is a conflict between Yoast and Elementor that has a knock-on effect on this plugin? Both plugins (and yours) are up-to-date.

We don’t have Yoast premium like @angelomusch. Do you think upgrading to premium would solve the issue?

Thanks,
Mark