Multisite Office Hours Recap (May 23, 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: @flixos90, @DrewAPicture, @richardtape, @ipstenu, @jeremyfelt

Tickets Covered

  • The commit for #34941 landed. This ticketticket Created for both bug reports and feature development on the bug tracker. will stay open for a bit to track any issues that come up and any new tests that are written. A dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. will be needed to describe the changes and hopeful lack of impact.
  • WP_Site_Query is now in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as part of #35791. There is still some work to do to implement get_sites() as a wrapper for queries and apply it throughout core, but we’re moving along. @jeremyfelt is going to work on getting that in shortly.
  • Once get_sites() is in, a ticket should be created to deprecate wp_get_sites() as it will no longer be useful.
  • #36935 was opened to lazy load details on WP_Site objects. This could allow for the deprecation of get_blog_details() in the future. For inspiration see #15458, which did something similar for user metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.. @flixos90 has a 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. up already.
  • #36717 introduces getters and issetters to WP_Site and WP_Network so that we can use better named properties for ID, network_id, etc… The topic of naming should be discussed in the core meeting first so that we can settle on id vs ID or something else.
  • #35379 and #18088 cover the differences in option sanitization between site and networknetwork (versus site, blog) options. There are good patches on both. @jeremyfelt will take a closer look this week.

If you aren’t available during the weekly multisite office hours, feel free to leave a comment here or in #core-multisite with a ticket number you’d like to see discussed.

See you next week!

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