Multisite Office Hours Recap (May 3, 2016)

Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site office hours are held every Tuesday at 16:00 UTC in #core-multisite. The next will be Tuesday 16:00 UTC. A more casual bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub is on Thursday 20:00 UTC.

The weekly agenda for the 4.6 cycle is to (a) address blockers and share status on bigger initiatives, then (b) walk through a few multisite focused tickets on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

Today’s chat log

Attendees: @ocean90, @flixos90, @spacedmonkey, @rachelbaker, @jeremyfelt, @johnjamesjacoby, @mikelking

Tickets Covered

There was some great conversation around a handful of tickets that took the hour.

  • #35791, WP_Site_Query has been continuing to make good progress. Existing coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. unit tests pass with the latest patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. These primarily test wp_get_sites(). Tasks for the next couple weeks include writing more new unit tests for WP_Site_Query() itself, testing the patches, and gathering additional feedback. The target commit date is May 12th. Please leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.! 🗒
  • #32504, WP_Network_Query is also looking like a possibility for the 4.6 cycle. Additional feedback on supported arguments and use cases for WP_Network_Query is more than welcome at this point.
  • Which brings us to naming. 🤓 We need to determine if get_sites() is appropriate or if we should stick with wp_get_sites(). The only trouble with the current form (wp_get_sites()) is that an array of arrays is returned rather than an array of objects. Introducing get_sites() would allow us to deprecate wp_get_sites() and follow previous work like get_posts(), get_users(), get_comments(). The same question exists for networks and get_networks(). A related ticket there is #29415.
  • And more naming. #36717 introduces magic getters so that id will be available on WP_Network and WP_Site objects, site_id will be available for the main site on a WP_Network object, and network_id will be available on a WP_Site object. The changes seem sane, there are probably a few additional details to sort out.

And a couple tickets left over from last week that should be mentioned to continue progress:

  • #15800 remains super close. @johnjamesjacoby is going to adjust the patch and we’ll see if it can go in this week.
  • #34941 would enjoy some review. This wraps a large chunk of the multisite bootstrap process, so the more eyes the better. 😅

#4-6, #multisite, #networks-sites