Replies: 0
Theme: Avada
Was updating one of their global elements and then 100’s of pages on the site failed to load.
about URL is one left with symptoms.
As we could not afford to have the site down.
Avada are saying your plugin had a table corruption and then corrupted their posts.
Weirdly but doing a full edit on the page not loading and saving it with no changes it then loads.
Disabling the fusion builder plugin used by the theme also results in page loading but obv then not formatted.
a quick edit and save doesn’t rectify the problem. This is the 3rd time this has happened in 4 months.
We have now deleted the plugin and removed the tables as cannot afford this to happen again. Either we go back to backup. Lose nn hrs of work.
Or spend hrs updating all the pages/posts which are affected. Very costly.
In php error log we had:
'PHP message: WordPress database error Duplicate entry '637-0' for key 'PRIMARY' for query INSERT INTOwp_yoast_indexable_hierarchy(indexable_id,ancestor_id,depth,blog_id) VALUES ('637', '0', '0', '1') made by do_action('wp_ajax_fusion_builder_update_layout'), WP_Hook->do_action, WP_Hook->apply_filters, Fusion_Builder_Library->update_layout, apply_filters('content_save_pre'), WP_Hook->apply_filters, FusionSC_Global->update_global_elements, wp_update_post, wp_insert_post, do_action('wp_insert_post'), WP_Hook->do_action, WP_Hook->apply_filters, 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->build, Yoast\\WP\\SEO\\Builders\\Indexable_Hierarchy_Builder->build, Yoast\\WP\\SEO\\Builders\\Indexable_Hierarchy_Builder->save_ancestors, Yoast\\WP\\SEO\
at exact time of the site going down. So it’s 100% related.
We installed Yoast Test and did the reset/truncate. we have phpmyadmin access.
Then we ran the SEO optimisation. This failed with a 503 error after several minutes.
This site does have a large no of pages and posts…
For now we’ve removed the plugin and tables on advice of Avada.
We’re quite experienced in both dev and seo so we can make do without to be honest.
But I’m not totally convinced the end result is 100% a Yoast problem or indeed the original error either….