Multisite Office Hours Recap (June 7, 2016)

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

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: @iamfriendly, @ipstenu, @spacedmonkey, @flixos90, @paaljoachim, @jeremyfelt

Tickets Covered

#35791, WP_Site_Query, is almost complete. It’s open as a task to help track any issues, but can probably be closed as fixed soon. Specific implementation can be handled in other tickets.
#36675, implementing WP_Site_Query in WP_MS_List_Table, is the biggest remaining piece at the moment. Patches are getting closer and will likely solve a handful of tickets when done—#33185, #24833, and #21837.
#36994 was committed after office hours and wp_get_sites() is now deprecated. It wraps the new get_sites() instead.
#32504, WP_Network_Query is still possible for 4.6. There’s 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. and tests. @jeremyfelt will review this week.
#36717 adds magic methods so that WP_Site and WP_Network have nicely named properties. It was committed after office hours and broke the routing of sites on w.org. 🔥 It has been reopened for further exploration. See comment 20 on the ticketticket Created for both bug reports and feature development on the bug tracker. for more information. @flixos90 has already been looking at the issue and how #36935 can help.
#37050 was opened because it would be nice if id was an int on WP_Network. The concern with this is that anything doing a strict comparison on a numeric string would break. Feedback please. 👋
#33900 introduces get_current_network_id() and is close to commit. @jeremyfelt will likely get that in today.
#18088 and #35379 are still on deck. @jeremyfelt owes reviews.

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

Welcome!

Communication

Tickets Covered

Share this:

Site resources