Plugin Support
Jerlyn
(@jerparx)
Hi @blackeye0013 ,
We are sorry to hear about the difficulties you are having. We understand you do not want to update your Elementor to the latest version and that you are getting an error when clicking the Yoast tab in Elementor Editor.
Incompatibility is to be expected if you are not running the latest versions (starting from the integration) of the plugins. Unfortunately, there is no way to disable the integration. You can work with the versions prior to the integration but we don’t recommend using an outdated version for the reasons discussed here.
Hi Jerlyn,
Really, there is no way to test the Elementor integration upon installed Elementor version and if the version doesn’t meet the requirements, just don’t load the integration? Do you feel it’s better to expect only the last version and throw an error if not?
I would expect you are running test wheather Elementor is installed, why not add it’s version too?
On the other hand, now I’ve got the last needed argument to convince the last client, who is still using Yoast to finally move away… 😉
P.S.: Yes, I know I should use the last versions possible, but it’s impossible when the last version has bugs preventing me from using it.
Hi Petr,
Sorry to hear that you’re not able to use the latest version of Elementor. Are you suggesting that Yoast SEO disables the Elementor integration or shows a warning that the Elementor version is not compatible?
If so, thank you for suggesting a new feature for one of our plugins. You can submit a feature request in our GitHub repo here: https://github.com/Yoast/wordpress-seo/issues/new/choose. It would be helpful to also report this to Elementor as well.
Just to explain a bit more, this integration relies on the changes to the code in the latest Elementor version and in Yoast SEO, so making changes to Yoast SEO alone would not result in Yoast SEO working as you expect.
We hope this helps you understand why this feature isn’t backward-compatible and we hope you’ll be able to update to the latest version at some point soon.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
