[wp-trac] [WordPress Trac] #37181: Use metadata api in *_network_options
WordPress Trac
noreply at wordpress.org
Fri Jul 28 13:44:39 UTC 2017
#37181: Use metadata api in *_network_options
-------------------------------------------------+-------------------------
Reporter: spacedmonkey | Owner:
Type: enhancement | Status: reopened
Priority: normal | Milestone: Future
Component: Options, Meta APIs | Release
Severity: normal | Version: 4.4
Keywords: has-patch needs-unit-tests ms- | Resolution:
roadmap | Focuses: multisite
-------------------------------------------------+-------------------------
Comment (by spacedmonkey):
In [https://core.trac.wordpress.org/attachment/ticket/37181/37181.2.diff
37181.2.diff] are the following changes
- wp_load_core_site_options now uses get_current_network_id to bring into
line with `_network_option` functions.
- serialize functions returned to `_network_option` functions which was
stopping tests from passing.
- `delete_network_option` uses `delete_metadata` and passes 4 param as an
empty string, as per meta api.
- meta.php and formatting.php moved to earlier in bootstrap process
because network options loaded ealier in bootstrap.
- Test added to prove that first value in meta store is honored.
- New update_network_meta_cache param added to wp_network_query. Network
options are primed in cache, like other query classes.
- Removed test_site_notoptions test, as no longer valid.
- Documentation. Poke @DrewAPicture for feedback.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/37181#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list