[wp-trac] [WordPress Trac] #37181: Use metadata api in *_network_options
WordPress Trac
noreply at wordpress.org
Tue Apr 4 23:55:06 UTC 2017
#37181: Use metadata api in *_network_options
----------------------------------------+------------------------------
Reporter: spacedmonkey | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Options, Meta APIs | Version: 4.4
Severity: normal | Resolution:
Keywords: has-patch needs-unit-tests | Focuses: multisite
----------------------------------------+------------------------------
Comment (by flixos90):
Briefly summarizing today's office-hours proposed goals:
* Introduce `*_network_meta()` functions using the Metadata API for direct
interaction with the `sitemeta` table.
* Add support for `meta_query` in `WP_Network_Query`.
* Use the new functions in the `*_network_option()` functions. This gives
performance benefits and allows us getting rid of the `alloptions` mess.
The `*_network_option()` functions will continue to maintain their current
hooks for BC, while the `*_network_meta()` functions will be clean as
other object metadata functions.
* Encourage using the new functions and use `*_network_meta()` in Core
going forward. The `*_network_option()` functions will stay around for BC
though, and should not be deprecated.
* This will also benefit a future `/networks` REST API endpoint.
See #37923 for related plans of introducing a `blogmeta` table and
surrounding `*_site_meta()` functions.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/37181#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list