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

[WordPress Trac]

#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                 |  Resolution:
 Keywords:  2nd-opinion has-patch  |     Focuses:  multisite
-----------------------------------+------------------------------

Comment (by johnjamesjacoby):

 The neat thing about codifying this approach, is we can start thinking
 about "network options" like the metadata that it is instead of by the
 screens & hard-coded settings with which that data is funneled through.

 A few less obvious wins:

 * Ability to register network meta, and use the sanitization & capability
 checks that come with `register_meta()`
 * Mirror `get_post_custom()` and have 1 function get "all meta" similar to
 the `alloptions` cache

 And maybe other caveats:

 * The settings API is not currently used in the Network Admin. Can we use
 these new functions with a network settings API?
 * So many wrappers. Is this worth added confusion of which to use when and
 why?
 * This matters more for multi-network than multi-site. Is this better
 handled in a plugin?

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