• Resolved ljupche

    (@ljupche)


    Hi,

    I have a quite large multisite with 3500+ sites and I need to update from v7.6.1 to v14.7. When updated the indexing process brought the server to a halt.
    I understand this needs to be done and there is a way for this to be done using a CLI command.

    My question is, is there a way to do this in a controlled manner with a few sites at a time?

    As I understand the indexing process starts when a site is visited. Is there a way to stop this and let the indexing be completed only from the CLI command?

    Thanks,
    Ljupche

Viewing 6 replies - 1 through 6 (of 6 total)
  • @ljupche

    The indexing process continues from where it was last stopped or paused. That means you can run the command at any time for your sites via CLI command only.

    Thread Starter ljupche

    (@ljupche)

    Hi Suwash,

    Thank you for the timely response. My question was can I stop the automatic indexing for all sites? I would like to control which sites are getting indexed and when.
    Otherwise as soon as I update the plugin on the multisite all 3500+ sites are getting indexed as soon as they are visited (which is almost immediately ) and brings down the server and the DB.

    Thanks,
    Ljupche

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi,

    Do you mean you want to stop the ‘lazy loading’ of the indexables that runs in the background?

    Unfortunately, there isn’t an option in the plugin settings to turn off or prevent the indexables from running in the background. We can only recommend that you run the indexables process through WP-CLI (especially for larger sites) – https://developer.yoast.com/features/wp-cli/reindex-indexables/

    Thread Starter ljupche

    (@ljupche)

    Hi Michael,

    Is there anything I could change in the code to stop the automatic indexing that occurs when the site is first visited after the upgrade?

    Thanks,
    Ljupche

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi @ljupche

    Seeing as the indexables are an integral feature so that our plugin functions as expected, I don’t believe there is a way to entirely disable the lazy loading of the indexables when a user visits the frontend URL of the posts and pages on your website.

    You may want to refer to our developer portal for more information. Sorry we can’t be of more help here.

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi,

    Setting this to closed in order to keep the forum overview.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Yoast update breaks server (Indexing)’ is closed to new replies.