[wp-trac] [WordPress Trac] #35773: _network_meta() functions could use _metadata() API

WordPress Trac noreply at wordpress.org
Mon Feb 8 05:30:07 UTC 2016


#35773: _network_meta() functions could use _metadata() API
--------------------------------+-----------------------------------
 Reporter:  johnjamesjacoby     |      Owner:
     Type:  enhancement         |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  Options, Meta APIs  |    Version:  3.0
 Severity:  normal              |   Keywords:  2nd-opinion has-patch
  Focuses:  multisite           |
--------------------------------+-----------------------------------
 The `wp_sitemeta` database table matches exactly the format expected by
 the Metadata API. It could use it out of the box, but a bunch of bespoke
 surrounding code would need updating:

 * `alloptions` cache keys would need tests
 * Filter names would need to be carried over or deprecated
 * Network ID fallbacks would need revisiting (sometimes primary ID is
 guessed)
 * Transients, if we tried integrating them, would need... probably a lot

 I'm attaching a basic & obvious first pass at how easy this could be, if
 it weren't for all the legacy stuff. This is a big-huge task that might
 not be worth exploring much more, but I figured I'd get some discussion
 going to start.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/35773>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list