WordPress.org

Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #51769, comment 9


Ignore:
Timestamp:
11/27/2020 03:25:19 PM (3 months ago)
Author:
zieladam
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #51769, comment 9

    v2 v3  
    1616* WP upgrade flow would attempt to create these indexes one time only. Perhaps we could reduce the number of people experiencing these timeouts by short-circuiting if `SELECT COUNT(*) from wp_posts` is a large number (how large?). Perhaps also short-circuit on multisites. Maybe we could also rely on some filters or otherwise provide a way out for those sites that really don't want to be upgraded.
    1717* If the indexes are successfully created, that's great and full-text search becomes available on the site. It could be enabled/disabled via site settings.
    18 * If the operation times out or otherwise fails, it will not be attempted again. Refreshed upgrade screen would include a short note about how Full-text search is available in WP 5.7 but could not be automatically enabled, and then link to a documentation page with further details. The same note would be displayed instead of the related site setting.
     18* If the operation times out or otherwise fails, it will not be attempted again. Refreshed upgrade screen would include a short note about how Full-text search is available in WP 5.7 but could not be automatically enabled, and then link to a documentation page with further details. The same note would be displayed instead of the related site setting. There could also be a `wp-cli` command to attempt the upgrade.
    1919
    2020In this scenario, the upgrade would be automatic and the failure would handled gracefully.