Thomas Kr?ftner

Thanks for your patience: This is now fixed in version 2.0.1 which we have just released. If you have any further issues please open a new topic.

Thanks for your patience: This is now fixed in version 2.0.1 which we have just released. If you have any further issues please open a new topic.

Thanks for your patience: This is now fixed in version 2.0.1 which we have just released. If you have any further issues please open a new topic.

This is fixed in version 2.0.1 which we have just released. If you have any further issues please open a new topic.

Is this an issue with Yoast SEO alone or something that only happens in combination with this plugin?

So, this was an annoying mistake, thanks for letting us know.
Unfortunately some time has passed while we were busy with other things and now we’re in a situation where already ~50% of all users have upgraded so we’d deactivate the plugin for half of the users in any case. Therefore we decided to leave things as they are. We’ll try to do our best to not let something like that happen again.

For more details on the decision process you can have a look at the issue on github if you want: https://github.com/Yoast/yoast-acf-analysis/issues/75

I am not sure what exactly it is that you want. Can you explain in more detail what you are trying to achieve?

This is currently not supported (and I assume also not easily added) but we have an issue on github for this. We’ll have a look at it to see what we can do, but I can’t promise anything for now.

I have just created an issue on Github for this: https://github.com/Yoast/yoast-acf-analysis/issues/97

Thanks for reporting. This should be covered by 2.0.1 which we are currently preparing for release.

Also see https://www.ads-software.com/support/topic/gettting-exception-after-activating-plugin/

Are there any more details what error that is?

Closing this as a duplicate of https://www.ads-software.com/support/topic/error-when-activating-plugin-33/

We are just finishing up a 2.0.1 release which should fix this soon. I’ll keep you updated.

Thanks for the report and the thorough investigation. We are aware of this and just finishing up a 2.0.1 release which should fix this soon. I’ll keep you updated.