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

[WordPress Trac]

#37923: Introduce shared wp_blogmeta database table for multisite installation
-------------------------------------------------+-------------------------
 Reporter:  johnjamesjacoby                      |       Owner:
     Type:  feature request                      |      Status:  new
 Priority:  normal                               |   Milestone:  Future
Component:  Networks and Sites                   |  Release
 Severity:  normal                               |     Version:
 Keywords:  has-patch dev-feedback has-unit-     |  Resolution:
  tests needs-testing                            |     Focuses:  multisite
-------------------------------------------------+-------------------------

Comment (by flixos90):

 Pasting my comments from Slack here:

 <slack>
 I think we should be talking about site and network meta together. While
 they don't need to happen at a similar time (maybe not even in the same
 release), we should have a clear fixed path going forward for both before
 we start finalizing/merging one of them.

 My opinion is that both should be introduced. Site meta for the reasons I
 outlined in #37923, and network meta because its API is more structured,
 standardized throughout core, and the db table was made for meta after
 all.

 Also I think their functions should be `*_site_meta()` and
 `*_network_meta()`. We have discussed that a couple times, and as far as I
 can remember we agreed on using current naming conventions for new
 functionality. The mixture is obviously terrible, and introducing new
 functions with the old naming will make it even harder to work our way
 away from it. The database, options etc can and should continue to have
 their legacy names, but all APIs should reflect what at some point was
 decided to be the terminology for... well, sites and networks.
 </slack>

 Also adding @jeremyfelt's comments from Slack:
 > I've been treating network meta as lower priority behind the `/sites`
 and `/users` endpoints and work to support that. I think we need to land
 those features before we start introducing other big changes.

 I agree with that statement, site meta should be introduced in the same
 release or soon after `/sites` as the endpoint will be another argument
 for introducing the table. Network meta could follow a bit later, as the
 change would also be more justifiable with a site meta API in place.

 Let's put this on our list of things to discuss in office-hours next week.
 From my POV the goal would be to also put #25344 in the "Future Release"
 milestone, but the primary objective should be determining a roadmap for
 both projects considered as a whole.

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