I have the same issue here. Can’t display breadcrumbs on my article. Those already displayed are working. Before that, I couldn’t even go on the edit page. WordPress was showing a debug page/ fatal error.
I just tried the new update. Here is one of the fatal errors that are still occurring:
Fatal error: Uncaught PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column ‘primary_focus_keyword’ at row 1 in /home/customer/www/uptownstories.org/public_html/wp-content/plugins/wordpress-seo/vendor_prefixed/j4mie/idiorm/idiorm.php:464 Stack trace: #0 /home/customer/www/uptownstories.org/public_html/wp-content/plugins/wordpress-seo/vendor_prefixed/j4mie/idiorm/idiorm.php(464): PDOStatement->execute() #1 /home/customer/www/uptownstories.org/public_html/wp-content/plugins/wordpress-seo/vendor_prefixed/j4mie/idiorm/idiorm.php(1983): YoastSEO_Vendor\ORM::_execute(‘INSERT INTO `wp…’, Array, ‘default’) #2 /home/customer/www/uptownstories.org/public_html/wp-content/plugins/wordpress-seo/src/orm/yoast-model.php(662): YoastSEO_Vendor\ORM->save() #3 /home/customer/www/uptownstories.org/public_html/wp-content/plugins/wordpress-seo/src/models/indexable.php(160): Yoast\WP\SEO\ORM\Yoast_Model->save() #4 /home/customer/www/uptownstories.org/public_html/wp-content/plugins/wordpress-seo/src/builder in /home/customer/www/uptownstories.org/public_html/wp-content/plugins/wordpress-seo/vendor_prefixed/j4mie/idiorm/idiorm.php on line 464
@stephanieohanley If you update to the most current version of Yoast SEO version 14.0.4, does this resolve the issue?
I’m not sure. They’ve updated and knock wood, so far have not reported any new problems now.
I will test again myself to see if ACF and Elementor are behaving properly and if the site’s speed is affected.
I will hear from them if Google Search Console alerts them to anything wonky.
I’ve used Yoast SEO for nine years and never saw anything like this update (these updates). I hope the problems people are reporting resolve soon.
@stephanieohanley Thanks for confirming that the 14.0.4 update appears to have resolved the issue for client. We’ll leave this post open but please let us know once you’ve had a chance to test whether the issue is resolved for yourself.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.