• Resolved Gravel

    (@g22)


    The latest plugin update (15.1.1) destroyed the whole website. My client (owner of the site) have lost a day of complete work because of this. This is really frustrating because I had to reload a backup of yesterday.

    Many users on this forums seems to encounter this fatal error which creates a huge error_log file. Mine was 437 GB, see screenshot for proof https://prnt.sc/v03jwe

    Reloading the backup from yesterday created an error_log of 1.8mb with different lines, here’s one that seems reccuring.

    [15-Oct-2020 20:26:35 UTC] Erreur de la base de données WordPress Table 'emoment_femmehockey.gf_yoast_indexable' doesn't exist pour la requête SELECT * FROMgf_yoast_indexableWHEREpermalink_hash= '29:0c215bd555e5535a142b929fd4fc91b3' ANDpermalink` = ‘https://femme.hockey/2020/10/’ LIMIT 1 faite par require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/kenozoik/full-width.php’), get_header, locate_template, load_template, require_once(‘/themes/kenozoik/header.php’), wp_head, do_action(‘wp_head’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Front_End_Integration->call_wpseo_head, do_action(‘wpseo_head’), WP_Hook->do_action, WP_Hook->apply_filters, 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_Post_Builder->build, Yoast\WP\SEO\Builders\Indexable_Link_Builder->build, Yoast\WP\SEO\Builders\Indexable_Link_Builder->create_links, array_map, Yoast\WP\SEO\Builders\Indexable_Link_Builder->Yoast\WP\SEO\Builders\{closure}, Yoast\WP\SEO\Builders\Indexable_Link_Builder->create_internal_link, Yoast\WP\SEO\Repositories\Indexable_Repository->find_by_permalink, Yoast\WP\Lib\ORM->find_one, Yoast\WP\Lib\ORM->run, Yoast\WP\Lib\ORM::execute
    `

    If I update the plugin to the latest version the same error repeats indefinitely until the hard drive of the server is full and crash.

    Please help, this is critical.

    I’m running a very healthy site with all best practices. PHP, SQL, WordPress, theme and plugins all updated to the latest version.

    Thanks for helping me.

    The page I need help with: [log in to see the link]

Viewing 16 replies (of 16 total)
  • Plugin Support devnihil

    (@devnihil)

    @g22 Can you please let us know whether you were able to perform any troubleshooting?

    Also, whereas we certainly understand not wanting to perform tests on a live site. Have you ever considered setting up a?staging environment?for your tests? This means that you can do all the testing and only change the live site when all works like intended

    Your host might be able to helpSome popular web hosts offer quick setups for a staging site so please contact your web host for assistance. They will probably be able to help you out.

    Alternative options to set up a staging environmentIf your web host does not offer staging sites, the WordPress plugin repository offers?staging?plugins?or you can?create your own staging site.

Viewing 16 replies (of 16 total)
  • The topic ‘CRITICAL ERROR after latest update’ is closed to new replies.