I don’t know if you ask the Yoast team or other people opinions.
But personally, I am still keeping track closely with their development. After seeing this issue: https://github.com/Yoast/wordpress-seo/issues/15051, I decided to not touch Yoast for now. Since my site has over 500k posts, I doubt it will work well in my situation.
Even with the 13.5 version, the sitemap is also useless. Because it crash server every times bot crawl the sitemap. It seem Yoast plugin is not ready for large sites..
In general. Sorry about that.
I’m not sure, if there’s any reason to go back to 13.5, now that we’re at 14.0.4… We’ve not seen any crashes in this version, but I’m still not sure how it’s performing the performance – if there’s any impact at all…
Thanks for your concern @exetico. As far as we know, we have seen some pretty good performance increase on some sites and some also failed due to several issues. While the 14.0 release didn’t work as flawlessly for everybody as we’d hoped, we are still hopeful for the new indexables feature.
In the Yoast SEO v14.0.4, we have fixed one of the most important bug. So, if you are already in the v14.* release, we do recommend you to update to the latest version as quickly as possible to have the latest fix in place.
In addition, our development teams are closely monitoring all the issues and reports that we have received so far and is already planned to be fixed with the next patch.
I was wandering the same and decided to wait for some time. Today I updated all my sites to 14.04. and already regret having done this. Three out of ten websites cause trouble and won’t do the re-indexing properly. It’s not the first time a major Yoast update cause massive issues, I thought with the fourth version it would be fine but it’s not. If I could undo it I would wait until 14.05 or later or better. 14.1….
Thanks for the answer, Mazedul.
@ceho – Damn. I just started the optimization on our site (30min. ago, or so), in 14.0.4. However, i created a backup… Let’s see, how it’s going. It’s currently half way to 100%, so i guess it’s (much) better than last time i tried, where it did fail multiple time, and crashed the DB, too. 🙂
I reverted all the websites to before the update.
Waiting to see if the new version gets patched and will then do a test to see if the indexables provide any measurable performance boost.
It’s a big change – it is common for such things to have problems.
Reported problems I saw, gave feedback. Response in general comes down to that it’s all good as far as developers are concerned “fewer than 5% of the websites are affected” – to quote from memory.
So I’ve decided to wait another month or so, then try again. Sticking with 13.5 for now.
Yoast has been the SEO plugin I’ve used since I started using WordPress (in 2015). Never been closer to switching to a different SEO plugin.
i reverted to 13.5
broken admin’ edit post with 14.0.4
PHP Warning: strlen() expects parameter 1 to be string, object given in /wp-content/plugins/wordpress-seo/src/models/indexable.php on line 160
PHP message: PHP Warning: md5() expects parameter 1 to be string, object given in /wp-content/plugins/wordpress-seo/src/models/indexable.php on line 160
PHP message: PHP Warning: mysqli_real_escape_string() expects parameter 2 to be string, object given in /wp-includes/wp-db.php on line 1158
PHP message: PHP Warning: trim() expects parameter 1 to be string, object given in /wp-content/plugins/wordpress-seo/src/presenters/canonical-presenter.php on line 48
PHP message: PHP Recoverable fatal error: Object of class WP_Error could not be converted to string in /wp-content/plugins/wordpress-seo/src/presenters/open-graph/url-presenter.php on line 45′, referer: /wp-admin/edit.php
i don’t know about sitemap, i use another plugin for that (bwp sitemap)
-
This reply was modified 3 years, 7 months ago by
crmb.
@exetico Were you able to successfully complete the optimization?
@crmb Please create a new issue if you are experiencing a similar problem as this helps us in tracking as this can be caused by many different variables (WordPress version, other plugins, etc).
Yes, at 14.0.4 it worked, like it should 🙂
