Multisite Office Hours Recap (May 12, 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.

4.3 ReleaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. Objectives

Our objectives for 4.3 can be split between UIUI User interface/UXUX User experience and back-end coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Here’s what we’re working on along with who is assigned or expressed interest in the past.

Networknetwork (versus site, blog) Adminadmin (and super admin) UI:

  1. Capture mobile flows and find areas to improve. @sofiarose, @kraftbj, @ubernaut
    • See last week’s office hours recap for a list of flows we’d like to capture
    • @hugobaeta has posted some desktop flow
    • This objective will likely mirror some of what the Admin UI group is doing. We’ll know more about individual opportunities as we dive in deeper.
  2. Combine scheme/domain/path in Add New Site and Edit Site workflows. @hugobaeta
    • When adding a new site, you should be able to just type the site’s new address without worrying about where to put each of the individual parts. https://wordpress.org should split into a scheme of https, domain of wordpress.org, and path of /
    • If an admin email is added that does not belong to an existing user, a user will be created with the site’s name and the user’s email address. There should be an opportunity to provide the user’s username and email in this scenario.
    • Related tickets: #22383, #31240, #14172, #14215
    • @hugobaeta will be working on some mock-ups
  3. Improvement of network upgrade workflow (ajaxify)
    • The current network upgrade process cycles through sites 5 at a time and processes the database upgrades. After each set of 5, the page refreshes and the next 5 are loaded. If one encounters an error, the entire process is stopped to await manual interaction. This should be something handled nicely via ajax.
    • Related tickets: #11869, #18292, #22589, #24922, #26056, #31405
    • @boren has posted a Mac/Chrome network upgrade flow

Multisite core:

  1. Provide validation for domains, paths, emails. @boonebgorges, @johnbillion, @jeremyfelt
    • The combined scheme/domain/path objective above relies on the validation of domains, paths, and emails. There are several quirky restrictions in multisite that would be nice to clear up. The first step is to establish validation functions so that we can write tests and then change the results as needed.
    • Related tickets: #17397, #18777, #20019, #19724, #21994, #15936, #16126, #17904, #26784
  2. Introduce WP_Site, WP_Network, WP_Site_Query, WP_Network_Query. @johnjamesjacoby, @earnjam, @rmccue, @jeremyfelt

If you’re interested in your name being attached to one of these objectives, please leave a comment here or a pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in #core-multisite.

There may be room for more, or reason to swap one of these with something else once we start progressing. Let’s keep the list about this size for now so that we have something consumable. We’ll continue to revisit these objectives weekly throughout the cycle.

#multisite