Issue After Updating to 17.6

  • Resolved diydoctor

    (@diydoctor)


    3 years ago

    Hi

    After upgrading to the lastest Yoast version 17.6 at the end of last week, without realising, this caused a wordpress database error in that the following error was occuring multiple times per second to teh point that it grew our php error log from it’s usual few bites in size to over 176GB in a matter of less than 3 days!

    The error that was occuring is as follows from the log file in question:

    [22-Nov-2021 10:41:07 UTC] WordPress database error Unknown column 'object_published_at' in 'field list' for query UPDATEwp_yoast_indexableSETobject_id= '1',object_type= 'user',permalink= '######################################',title= NULL,description= NULL,is_cornerstone= '0',is_robots_noindex= '0',is_robots_nofollow= NULL,is_robots_noarchive= NULL,is_robots_noimageindex= NULL,is_robots_nosnippet= NULL,is_public= NULL,has_public_posts= '0',blog_id= '1',open_graph_image= '######################################',open_graph_image_id= NULL,open_graph_image_source= 'gravatar-image',open_graph_image_meta= NULL,twitter_image= '######################################',twitter_image_id= NULL,twitter_image_source= 'gravatar-image',object_published_at= '2020-08-11 14:14:50',object_last_modified= '2021-11-22 06:54:28',version= '2',permalink_hash= '######################################',updated_at= '2021-11-22 10:41:07' WHEREid= '1' made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('######################################'), get_header, locate_template, load_template, require_once('/themes/genesis/header.php'), wp_head, do_action('wp_head'), WP_Hook->do_action, WP_Hook->apply_filters, wp_robots, apply_filters('wp_robots'), WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Front_End\WP_Robots_Integration->add_robots, Yoast\WP\SEO\Integrations\Front_End\WP_Robots_Integration->get_robots_value, Yoast\WP\SEO\Memoizers\Meta_Tags_Context_Memoizer->for_current_page, Yoast\WP\SEO\Repositories\Indexable_Repository->for_current_page, Yoast\WP\SEO\Repositories\Indexable_Repository->find_by_id_and_type, Yoast\WP\SEO\Repositories\Indexable_Repository->upgrade_indexable, Yoast\WP\SEO\Builders\Indexable_Builder->build, Yoast\WP\SEO\Builders\Indexable_Builder->save_indexable, do_action('wpseo_save_indexable'), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Watchers\Indexable_Post_Watcher->updated_indexable, Yoast\WP\SEO\Integrations\Watchers\Indexable_Post_Watcher->update_has_public_posts, Yoast\WP\SEO\Repositories\Indexable_Repository->find_by_id_and_type, Yoast\WP\SEO\Repositories\Indexable_Repository->upgrade_indexable, Yoast\WP\SEO\Builders\Indexable_Builder->build, Yoast\WP\SEO\Builders\Indexable_Builder->save_indexable, Yoast\WP\SEO\Models\Indexable->save, Yoast\WP\Lib\Model->save, Yoast\WP\Lib\ORM->save, Yoast\WP\Lib\ORM::execute

    Although reindexing the indexables via the Yoast Test Helper tool cleared the issue and stopped it occuring obiously we don’t want the issue occuring again as it filled our entire HD preventing any uploading or publishing of new posts, how can we prevent this occuring again??

    KInd Regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Michael Ti?a

    (@mikes41720)

    Hi @diydoctor

    While we aren’t familiar with your setup, based on the changelog for Yoast SEO v17.6, there wasn’t any mention of an enhancement or fix on the indexables database end.

    We understand you’ve reset the indexables using the Yoast Test Helper plugin. Did you already redo and complete the SEO data optimization process?

    If so, could you check and monitor if you are still receiving the same WordPress database error Unknown column 'object_published_at' in 'field list' for query UPDATE error from your server logs?

    Thread Starter diydoctor

    (@diydoctor)

    Hi

    We are just running a standard setup, nothing special at all with limited plugins so should not affect in any way any updates.

    I presume that when I used the test helper plugin to reset the indexable then this would have automatically started the SEO data optimisation process as there are no messages in the plugin settings anywhere that mention that this needs to be manually started??

    I have also checked the logs and we are no longer receiving the WordPress database error message

    Kind Regards

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi @diydoctor

    We’re glad to hear that you are no longer receiving the WordPress database errors after resetting the indexables.

    You can go to your WP admin dashboard > SEO (sidebar) > Tools and you can click on the ‘start the SEO data optimization process’ button for it to re-run.

    However, even if you don’t click on this button to start the process, it will lazily load the indexables over time as you and your users visit and crawl the website.

    Thread Starter diydoctor

    (@diydoctor)

    Hi

    Many thanks for confirming in terms of indexables, much appreciated

    KInd Regards

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi,

    We’ll be setting this forum thread to resolved.

    Thank you!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Issue After Updating to 17.6’ is closed to new replies.