sandraculi

Hi again!

So I found the file and I can see a few things. Errors start on the 14th of January 2021, before there weren’t many errors at all.

This is where the errors start, I’m not really sure what this error is about. It only seems to appear once though:

[14-Jan-2021 11:47:14 UTC] WordPress databasefout Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs bij query ALTER TABLEwp_yoast_indexableADDestimated_reading_time_minutesint(11) gemaakt door require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, wpseo_init, WPSEO_Meta::init, WPSEO_Options::get, WPSEO_Options::prime_cache, WPSEO_Options::get_all, WPSEO_Options::get_options, WPSEO_Options::get_option, get_option, apply_filters('option_wpseo_titles'), WP_Hook->apply_filters, call_user_func_array, WPSEO_Option->get_option, WPSEO_Option->array_filter_merge, WPSEO_Option->get_defaults, WPSEO_Option_Titles->enrich_defaults, YoastSEO, Yoast\WP\SEO\Main->load, Yoast\WP\SEO\Loader->load, Yoast\WP\SEO\Loader->load_initializers, Yoast\WP\SEO\Initializers\Migration_Runner->initialize, Yoast\WP\SEO\Initializers\Migration_Runner->run_free_migrations, Yoast\WP\SEO\Initializers\Migration_Runner->run_migrations, Yoast\WP\SEO\Initializers\Migration_Runner->run_migration, Yoast\WP\SEO\Config\Migrations\AddEstimatedReadingTime->up, Yoast\WP\Lib\Migrations\Migration->add_column, Yoast\WP\Lib\Migrations\Adapter->add_column, Yoast\WP\Lib\Migrations\Adapter->execute_ddl, Yoast\WP\Lib\Migrations\Adapter->query

Then, this error message appears and that one keeps on repeating for many different recipes:

[14-Jan-2021 12:17:09 UTC] WordPress databasefout Unknown column 'estimated_reading_time_minutes' in 'field list' bij query UPDATEwp_yoast_indexableSETobject_id= '11960',object_type= 'post',object_sub_type= 'post',permalink= 'https://culi-sandra.nl/?p=11960',primary_focus_keyword_score= NULL,readability_score= '90',is_cornerstone= '0',is_robots_noindex= NULL,is_robots_nofollow= '0',is_robots_noimageindex= NULL,is_robots_noarchive= NULL,is_robots_nosnippet= NULL,open_graph_image= NULL,open_graph_image_id= NULL,open_graph_image_source= NULL,open_graph_image_meta= NULL,twitter_image= NULL,twitter_image_id= NULL,twitter_image_source= NULL,primary_focus_keyword= NULL,canonical= NULL,title= NULL,description= NULL,breadcrumb_title= 'Crackers met ricotta en passievrucht',open_graph_title= NULL,open_graph_description= NULL,twitter_title= NULL,twitter_description= NULL,estimated_reading_time_minutes= NULL,author_id= '1',post_parent= '0',number_of_pages= NULL,post_status= 'draft',is_protected= '0',is_public= '0',has_public_posts= NULL,blog_id= '1',schema_page_type= NULL,schema_article_type= NULL,permalink_hash= '31:162825d7e8c00a14dbe3c21a59109217',updated_at= '2021-01-14 12:17:09' WHEREid= '2751' gemaakt door require('wp-blog-header.php'), wp, WP->main, WP->parse_request, do_action_ref_array('parse_request'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, call_user_func, WP_REST_Autosaves_Controller->create_item, wp_update_post, wp_insert_post, do_action('wp_insert_post'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Yoast\WP\SEO\Integrations\Watchers\Indexable_Post_Watcher->build_indexable, Yoast\WP\SEO\Builders\Indexable_Builder->build_for_id_and_type, 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

Another error that keeps on appearing is this one, this one started appearing on the 28th of Feb which I believe is around the time I found out something was off. This one also caused many error logs when I activated the plugin for a little while two days ago:

[28-Feb-2021 11:17:57 UTC] WordPress databasefout Duplicate entry '114-0' for key 'PRIMARY' bij query INSERT INTOwp_yoast_indexable_hierarchy(indexable_id,ancestor_id,depth,blog_id) VALUES ('114', '0', '0', '1') gemaakt door require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/sitka/single.php'), get_header, locate_template, load_template, require_once('/themes/sitka/header.php'), wp_head, do_action('wp_head'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Yoast\WP\SEO\Integrations\Front_End_Integration->call_wpseo_head, do_action('wpseo_head'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Yoast\WP\SEO\Integrations\Front_End_Integration->present_head, 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\Builders\Indexable_Builder->build_for_id_and_type, Yoast\WP\SEO\Builders\Indexable_Builder->save_indexable, do_action('wpseo_save_indexable'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Yoast\WP\SEO\Integrations\Watchers\Indexable_Ancestor_Watcher->reset_children, array_walk, Yoast\WP\SEO\Integrations\Watchers\Indexable_Ancestor_Watcher->update_hierarchy_and_permalink, Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build, Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->save_ancestors, Yoast\WP\SEO\Repositories\Indexable_Hierarchy_Repository->add_ancestor, Yoast\WP\Lib\Model->save, Yoast\WP\Lib\ORM->save, Yoast\WP\Lib\ORM::execute

[01-Apr-2021 08:22:52 UTC] WordPress databasefout Duplicate entry '3093-0' for key 'PRIMARY' bij query INSERT INTOwp_yoast_indexable_hierarchy(indexable_id,ancestor_id,depth,blog_id) VALUES ('3093', '0', '0', '1') gemaakt door require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/sitka/single.php'), get_header, locate_template, load_template, require_once('/themes/sitka/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\Builders\Indexable_Builder->build_for_id_and_type, 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_Ancestor_Watcher->reset_children, array_walk, Yoast\WP\SEO\Integrations\Watchers\Indexable_Ancestor_Watcher->update_hierarchy_and_permalink, Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build, Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->save_ancestors, Yoast\WP\SEO\Repositories\Indexable_Hierarchy_Repository->add_ancestor, Yoast\WP\Lib\Model->save, Yoast\WP\Lib\ORM->save, Yoast\WP\Lib\ORM::execute

BR, Sandra

Hi there,

I’ve dared to reactivate the plugin ?? My recent posts are still loading veeeeeery slow although not resulting in a 500 error. The strange thing is, this is only happenening in recent posts (published after half Feb). Older posts load quickly as usual.

So I’m afraid I can’t get to an errorlog. Will this comparison help to give more insights?

Newer post, loading time 20 seconds:
https://gtmetrix.com/reports/culi-sandra.nl/toCwkxRj/

Older post, loading time 3.5 seconds:
https://gtmetrix.com/reports/culi-sandra.nl/n9KjVJwv/

I will disable the plugin again now.

BR, Sandra

Hey there,

OK, so the host referred me to the location where I can download error logs. Would it be possible to upload these somewhere so you could review them? That would be amazing, I’m a total n00b with this ??

Or maybe you could point out what to look for in the files?

BR, Sandra

Hey there!

Yes, I’ve updated to version 5.7 of WordPress and YOAST version 16.0.2 recently and unfortunately the issue was still there after the updates.

I have indeed done what you described (deactivate all other plugins and switch to the standard theme) but that didn’t work either.

BR, Sandra

Hi Sumit,

In that case, I still don’t understand how some articles are prioritised over others? I get the logic, but it seems that the plugin doesn’t take into account how relevant an article is?

In my example of searching for ‘American pancakes’ on my blog, the top result you get is this blogpost:
https://culi-sandra.nl/weekmenu-14-kipschotel-traybake-american-pancakes/

As you can see, ‘American pancakes’ is present in the title, but in the article itself it’s only mentioned 2 times.

How can this be prioritised over the actual article about American pancakes, where the sentence is used 10 times? https://culi-sandra.nl/american-pancakes-recept-de-lekkerste/

BR, Sandra

Thanks, that did the trick!!

I have exactly the same issue on my blog (culi-sandra.nl) so I deactivated the plugin now.

i.e. when searching for ‘gerookte kip’ (smoked chicken) it comes up with search results for f.e. ‘gerookte zalm ‘ (smoked salmon) rather then prioritising the smoked chicken.

Ahhh, found it! Thanks ??

Hey there, it seems this still is an issue, my organic search results still show the standard caloriecount in the rich snippet.

And it seems a similar issue occurs when leaving the preparation time blank.

For example for this recipe:
https://culi-sandra.nl/linzenschotel-met-spek-paprika-en-champignons/

You can see that the preptime is 20 minutes. However the rich snippet, shows a preptime of 50 minuten (probably becuase the standard ‘prep time’ field is set on 30 minutes, but if I leave that field blank, it shouldn’t calculate this preptime normally, right?)

You can see the rich snippet here (first organic search result)

https://www.google.com/search?q=linzenschotel+spek+paprika&rlz=1C1GCEA_enDK802DK803&oq=linzenschotel+spek+paprika&aqs=chrome..69i57j0l2j69i60l3.2686j0j7&sourceid=chrome&ie=UTF-8

Thanks for the reply @devnihil ! I’ll feed this back to the developer of the plugin.

Hey there, thanks for the quick reply! The deactivation of the plugin indeed did the trick ??

Thanks, Sandra