[wp-trac] [WordPress Trac] #37923: Introduce shared wp_blogmeta database table for multisite installation

WordPress Trac noreply at wordpress.org
Tue Apr 4 23:48:58 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 flixos90):

 As discussed during today's office-hours, we're probably going for
 introducing the `blogmeta` table unrelated to our original plans for an
 options index, which needs to be investigated independently, since
 `blogmeta` is probably not the right approach, as determined during recent
 discussions.

 Main benefits:
 * Enables developers to store arbitrary data about a site in the multisite
 scope.
 * Opens up the future `/sites` REST API endpoint for developers so that
 they can `register_meta()` for sites that is handled by the API (both read
 and write access, will be implemented in the actual endpoint for which no
 ticket has yet been created).
 * Allows more flexible querying in `WP_Site_Query`.
 * Brings parity with other core objects, all of which have metadata
 tables.

 Related: We are likely going to introduce `*_network_meta()` API functions
 as well (see #37181), the table is already in place.

 [attachment:37923.diff] is an updated patch that only contains the
 `blogmeta` table and its surrounding API. The PR at
 https://github.com/jeremyfelt/wordpress-develop/pull/3 has been updated as
 well; however, since the introduction of this table is a much more
 straightforward process and since there were some merge conflicts with the
 previous patch that I already resolved in [attachment:37923.diff], I'd
 prefer if we continued to work on this through patches from now on.

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


More information about the wp-trac mailing list