[wp-trac] [WordPress Trac] #34091: Errors thrown after wp_termmeta table created but db updates not yet run

[WordPress Trac]

#34091: Errors thrown after wp_termmeta table created but db updates not yet run
-----------------------------+---------------------------
 Reporter:  morganestes      |       Owner:  boonebgorges
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  4.4
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:  fixed
 Keywords:                   |     Focuses:
-----------------------------+---------------------------

Comment (by boonebgorges):

 In [changeset:"34719"]:
 {{{
 #!CommitTicketReference repository="" revision="34719"
 Prevent Multisite term tests from hitting database for 'db_version'.

 [34718] introduced a 'db_version' check to term meta functions, to ensure
 that
 they don't run when the term meta schema is not yet in place. This call to
 `get_option()` causes a database hit during Multisite tests, due to the
 presence of the `WP_INSTALLING` constant. See #31130. The extra database
 queries are causing cache tests to fail.

 In similar cases, we have `markTestSkipped()` when `is_multisite()`.
 Because
 the term meta API is so extensive - term meta caches can be primed
 anywhere a
 `WP_Query` loop is fired up - we implement a more generous workaround in
 this
 case. To prevent `get_option( 'db_version' )` from hitting the database
 during
 multisite unit tests, we use a 'pre_option_' filter.

 Heaven help us.

 See #34091.
 }}}

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