Here is an update from our developers:
There are some known compatibility issues between Toolset Blocks and Yoast SEO plugin, for example:
https://toolset.com/forums/topic/toolset-blocks-is-not-ready-for-yoast-seo-analyzer/
Our developers are aware of those issues, and they are still in our to-do list, but this will probably not arrive soon.
I will keep on updating here if there is any news.
Thanks for letting me know that the developers are aware of some compatibility issues between Toolset Blocks and Yoast SEO.
I've had a look at the link you gave me: https://toolset.com/forums/topic/toolset-blocks-is-not-ready-for-yoast-seo-analyzer/
That link seems to be about a feature request so that Toolset sends text / shortcodes to Yoast so that the dynamic content (i.e. the presence of links) can be recognized properly for their SEO analyzer.
My ticket is about a bug that results in IP blacklisting by my webhost. Although I can whitelist my development IP, there are multiple users on the client side that doesn't make whitelisting a permanent solution. Currently, I can either use Toolset or Yoast SEO, but not both at the same time if I need a dynamic image.
Something coded in the Toolset Image block (using a dynamic source) is different from the other toolset blocks (using a dynamic source). For example, the Toolset header block (using dynamic content) works fine with Yoast SEO.
Can you confirm for me that the developers are aware of this distinction between this support ticket and https://toolset.com/forums/topic/toolset-blocks-is-not-ready-for-yoast-seo-analyzer/
Is there a temporary work around so that I can get a proper dynamic image url from Toolset? Why does the dynamic image load properly but create an error in the console?
Thanks for your ongoing help.
Yes, they are different issue, but both are compatibility issues Yoast SEO plugin, and have been escalated to our developers, I will update here if there is any news.
Any update on a fix for this? Seems this is still an issue over a year later as we too had our IPs blocked due to our host thinking it was malicious code execution with the shortcode being posted to the admin as a url.
@richardB-19, this issue was already escalated as a compatibility issue, and we have added your comment to our to-do list, our developers are working on it, but I am not sure when will it be fixed, will update here if there is anything news.
Do compatibility issues like this typically take over a year to get resolved? I could understand if this was this year that the issue was raised, but this is over a year and the issue still exists. I had multiple IPs blocked and have the same problem for our client as well.
Has this issue been resolved? I noticed that it started in early 2020 and I really appreciate the detailed exchange between mike-F2 and Luo Yang. But, to paying customers who are building sites with Toolset, I believe a public response is necessary. Yoast is a widely used and necessary plugin.
We have had this IP-blocking problem occur a number of times, from multiple computers/IP addresses, using WP Engine as the web host. After contacting WPE, they whitelist the IP and we can get back to work, but this is no way to work.
In the latest version of this problem, all we did was attempt to add a View to our homepage. When selecting a View, upon clicking "use this view" the website goes dead and is inaccessible. WPE stated: "The IP was blocked due to the number of "evil" hits detected from the system. By definition, these are caused by URL requests with single quotes in the URL." I have attached an image showing the problem code that WPE sent us. It appears to involve a featured image, similar to the problem mike-F2 originally reported.
Thank you.
