[wp-trac] [WordPress Trac] #37923: Introduce shared wp_blogmeta database table for multisite installation
WordPress Trac
noreply at wordpress.org
Wed Mar 29 04:14:18 UTC 2017
#37923: Introduce shared wp_blogmeta database table for multisite installation
------------------------------------------------+--------------------------
Reporter: johnjamesjacoby | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting
Component: Networks and Sites | Review
Severity: normal | Version:
Keywords: 2nd-opinion has-patch dev-feedback | Resolution:
| Focuses: multisite
------------------------------------------------+--------------------------
Comment (by johnjamesjacoby):
Another caveat: core's existing `_site_transient()` functions make
`_site_meta()` function names confusing.
Yes... we all pretty much understand functions with `_site_` in their name
could mean blogs or networks, not pointing at the same object or database
table. But transients, meta, and options traditionally are saved in the
same place, and if we introduce a `_blogmeta` database table, it's
plausible we might want `_blog_transient()` functions also.
* Do we want `_blog_meta()` functions instead, to match the `_blogmeta`
table?
* Do we want to easily enable transients to exist in `_blogmeta` vs (or in
addition to) `_options`?
* My plugin uses `_blog_` for function names instead of `_site_` and I'd
like to update it to whatever direction we think is best for WordPress
core going forward, before adoption rises and backwards compatibility
becomes a concern.
* Should we add a `wp_` prefix to any new transient functions, to allow
both site & network transients? Then we could deprecate the old
`_site_transient()` functions with new `wp_*_network_transient()` ones?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/37923#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list