WPSEO_Frontend obsolet

@tehfo,

Sorry for the trouble.

Please make sure that you’ve updated your AMP plugin along with Yoast SEO 14.0.4.

If that doesn’t help, try clearing the cache from your theme, plugin, server, browser and CDN (e.g. CloudFlare). If you are not sure how to clear the cache from a theme or plugin please speak to those authors. If you want to clear cache from the server, please speak to your host provider. To clear the cache from a browser use this guide: https://kb.yoast.com/kb/how-to-clear-my-browsers-cache/.

Let us know how this goes.

Suwash, thanks for your answer and help in advance! ??

I chedked and the plugin is updated to 14.0.4;
Checked and autoptmize was cache cleared, but to make sure I cleared it again…
And the CDN cache was also cleared… But to make sure I invalidated the cache on the CloudFront again.

But, still getting the error. I acessed the blog via the “direct” server (without CDN) and it’s also with the error.

Tried to access everything in a anonymous browser and still got the error. ??

Deprecated: WPSEO_Frontend::canonical está obsoleto desde a vers?o WPSEO 14.0 sem nenhuma alternativa disponível. in /var/www/html/wp-includes/functions.php on line 4723
lang=”pt-BR”>
Deprecated: WPSEO_Twitter::get_instance está obsoleto desde a vers?o WPSEO 14.0 sem nenhuma alternativa disponível. in /var/www/html/wp-includes/functions.php on line 4723
Deprecated: WPSEO_OpenGraph::__construct está obsoleto desde a vers?o WPSEO 14.0 sem nenhuma alternativa disponível. in /var/www/html/wp-includes/functions.php on line 4723

Based on the information you provided, we expect this to be a bug. We’re actively using the bug tracking on our GitHub repository so your best next step would be to create a new issue for our developers at https://github.com/Yoast/wordpress-seo/issues/new. You will need an account to create a new issue. If this is your first bug report, please check out: https://kb.yoast.com/kb/how-to-write-a-good-bug-report/.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Ok… The bug is on github :). thanks!