Multisite Office Hours Recap (October 13, 2015)

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 20:00 UTC in #core-multisite. The next will be 2015-10-20 2000.

Today’s chat log
Overall 4.4 Release Objectives

Rough ticketticket Created for both bug reports and feature development on the bug tracker. agenda posted before the meeting:

  • #28290_network_option() is in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. with the new parameter order. Is there anything else we should do on this ticket? I’m thinking global options stored as networknetwork (versus site, blog) id 0 should be a new ticket.
  • #31985WP_Network() – Thoughts on making properties private and adding getters? I’m okay with leaving them public, though there’s no turning back. 🙂
  • #34065 – How often is the network setup screen used to create a new network with another user as the network adminadmin (and super admin)? Should we just bail early with a message or think about refactoring this?
  • #20104 – Marked as commit, toss thoughts in now if you haven’t… 🙂
  • #34287 – Value of a “Settings” link under the Network Admin menu?
  • Open floor


  • #28290
    • Where does _network_option() belong? It has to stay in options.php because we wrap with _site_option() now. Moving to a new ms-options.php or similar would mean including that file anyway during single site load.
    • Are we leaving anything on the table? Requesting comments on this one. We’re happy with _network_option() as it is and happy including to have it in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Does anyone have concerns with the current state?
    • We’ll want to close this ticket pre-betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. (one week), so leave your comments! 🙂
  • #31985WP_Network(). We seem okay here. Going to stick with public properties to meet general assumptions and to avoid back-compat errors with the existing $current_site. We can bring up additional enhancements in new tickets. Ticket closed as fixed.
  • #34065 – This opened a larger can of worms around what “network admin email” means in #34293. In the meantime, we can address this ticket with a few assumptions. Added note to ticket.
  • #20104 – Everybody is happy. Ticket committed. Those who can manage network plugins now see the status of those network plugins in the site admin.
  • #34287 – We had a collective +1 on adding “Settings” to the Network Admin menu. Ticket committed.
  • #34293New ticket. @ipstenu updated with some conclusions and clarifications so we can keep the discussion going. We should update messaging around the several different types of emails used to send or receive notifications in multisite.

Thanks everyone!