Multisite 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 bug 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 Trac 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, @jeremyfelt, @boonebgorges, @rachelbaker, @earnjam, @iamfriendly, @johnjamesjacoby
- @flixos90 has been working on #15691 and is requesting feedback. @jeremyfelt will take a look this week. @boonbgorges also has it on his list. More welcome!
- Somewhat related to that are #18088, #35698, and #35379, which require more context when sanitizing network (versus site, blog) options so that they are treated differently than site options. These are all on the 4.6 milestone now and shouldn’t be far off from commit.
- #16001 and #31127 need testing and exploration to determine solutions. @richardtape has dug in and @earnjam will be as well.
WP_Site_Query is moving along nicely, thanks @spacedmonkey! @flixos90 is going to take a closer look at the latest patches. @jeremyfelt will as well. If anyone would like to dive in on unit tests, now is the time. ⚡️
WP_Network_Query is a possibility for 4.6. @flixos90 will start playing with a patch 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..
- #34941 needs review, and @johnjamesjacoby will be taking a look at it. This wraps a large chunk of the multisite bootstrap process, so the more eyes the better. 😅
- #27287 and #36507 both deal with unexpected or incorrect URLs when multisite is installed in a subdirectory. In general—see #19796—multisite installs should work with WordPress in a subdirectory. Any patch to resolve issues here should ensure wide coverage with unit tests so that we don’t affect current behavior.
- #15800 is super close. @johnjamesjacoby is going to adjust the patch and we’ll see if it can go in this week.
- #36546 and #24617 are both closed as fixed. Spammed users can no longer log in or reset their password.
That’s that. See you next week!