[wp-trac] [WordPress Trac] #54849: Site transients cause DB errors when installing

[WordPress Trac]

#54849: Site transients cause DB errors when installing
--------------------------------+---------------------
 Reporter:  peterwilsoncc       |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  5.9.1
Component:  Options, Meta APIs  |     Version:  5.9
 Severity:  normal              |  Resolution:
 Keywords:  has-patch           |     Focuses:
--------------------------------+---------------------

Comment (by peterwilsoncc):

 Replying to [comment:7 tnolte]:
 > So we have a setup where the `WP_CONTENT_DIR` is being set because we
 install WordPress Core in a subdirectory using Composer. Seeing the
 details in this report I can see how this didn't get caught since this
 customization is probably atypical for a new install.

 Thanks for your understanding, I use such an environment for my wordpress-
 develop environment but missed it because I don't often need to do a fresh
 install.

 In your blog post, I see you were getting the error with `options` tables
 rather than `sitemeta` tables -- that's caused by a difference with the
 storage of site wide transients in multi-site vs single-site mode.

 ----

 In the [https://github.com/WordPress/wordpress-develop/pull/2250 linked
 pull request] I've got a proof of concept to prevent transients from using
 the database if `wp_installing() === true`. This ought to prevent the
 database errors during installation.

 My inclination is that it will need additional work, especially for site
 transients on a multisite install.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54849#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform