Impossible to update beyond version 13.5

  • Resolved bradlol

    (@bradlol)


    5 years, 1 month ago

    I was on version 12.8.1 and decided to finally update.
    First it couldn’t go through because of ALTER on link table, which took about 30min before I stopped it. Then I decided to truncate that table.
    Update went through and then my database got flooded with
    SELECT post_id, meta_value FROM wp_postmeta WHERE meta_key = '_wp_attached_file' AND meta_value = '?' queries to the point it hit my connection limit.
    I was doing it at night and even when my site is least busy it was impossible to access site. When I test that query it takes about 7 seconds. I have over 1m posts and my postmeta table has over 12m rows.
    I had to reverse to version 13.5, any update beyond that version is probably impossible for me.

    Is there any way to update for me? Can I disable lazy indexing (I guess that’s the issue) and just index through CLI(probably bad idea anyway because it will take ages)?

Viewing 6 replies - 1 through 6 (of 6 total)
  • devnihil

    (@devnihil)

    5 years, 1 month ago

    @bradlol We’re sorry to hear you are experiencing this issue on your site.

    Can you please first confirm you are using WordPress 5.7.1? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: https://yoast.com/why-we-dont-support-old-wordpress-versions/

    Also, as a workaround, you can also perform a manual update of the plugin. We have instructions on how to upgrade the plugin manually at the following link: https://yoast.com/help/how-can-i-update-my-free-plugin/#ftp. You will need an FTP program such as FileZilla and your FTP details, which can be obtained from your host provider.

    Thread Starter bradlol

    (@bradlol)

    5 years, 1 month ago

    I’m on WordPress 5.6. I don’t think 5.7.1 would change anything.

    As for manual update, would it stop indexables from lazy loading?

    Md Mazedul Islam Khan

    (@mazedulislamkhan)

    5 years, 1 month ago

    Thanks for your confirmation. If you perform the indexing using WP-CLI, we are expecting to resolve the issue for you as whenever the indexing remains empty, Yoast SEO automatically runs the indexing behind the page when someone visits a particular page on your website.

    So, it’s better to perform the indexing through WP-CLI and that will stop the indexing process entirely once it’s completed. You can find the relevant WP-CLI specific command here: https://developer.yoast.com/features/wp-cli/reindex-indexables/

    Thread Starter bradlol

    (@bradlol)

    5 years, 1 month ago

    Ok, I tried that. I ran that command on WP-CLI, but it didn’t seem to stop lazy indexing, as my database still got flooded with those queries.
    Anyway WP-CLI wouldn’t be an option either. Having in mind I have over 1m posts and that single query takes around 7s(on least busiest time), indexing posts would take over 3 months. I also have over one 1m users and 200k+ terms, so god knows how long it would take to index it all.

    Plugin Support Michael Tiña

    (@mikes41720)

    5 years, 1 month ago

    Hi,

    We’re not exactly sure what else to recommend, because if lazy loading of the indexables in the background or running the SEO data optimization process on the WordPress dashboard isn’t an option due to the size of the website, we normally would recommend running the indexables through WP-CLI as that would be a less taxing option, especially for larger websites — https://developer.yoast.com/features/wp-cli/reindex-indexables/

    We might need to take a closer look at your setup to see if there’s anything else we can recommend, but we are unable to do so here. You might want to consider Yoast SEO Premium so we can perhaps see if there are any alternatives once we’ve taken a closer look at your website.

    devnihil

    (@devnihil)

    5 years, 1 month ago

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Impossible to update beyond version 13.5’ is closed to new replies.