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 20:00UTC in #core-multisite.
We had a lively conversation today around some of our objectives for the 4.3 cycle. The conversation was mostly focused around creating a visual record for the current network (versus site, blog) admin (and super admin) UI User interface and then establishing our goals for moving that forward. @hugobaeta, @sofiarose, @ubenaut, and @kraftbj all volunteered to start capturing workflows for devices. There are a lot of good notes in #core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-flow and examples of other visual records on make.wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//flow we can use as a launch point.
Here’s an initial prioritized list of some common workflows. Please add and/or discuss in the comments. I’m likely missing many things. 🙂
- Add a new user to a site when the user does not currently exist as a network user.
- Add a new user to a site when the user does exist as a network user.
- Install, enable, and then activate a theme for a single site on the network.
- Install a theme and enable it for use on a network.
- Install and then activate a plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party for use on a single site on the network.
- Install and then network activate a plugin.
- Setup multisite from scratch in a subdirectory configuration.
- Setup multisite from scratch in a subdomain configuration.
- Create a new site on the network.
- Upgrade WordPress, including the network upgrade.
- Update a plugin.
- Update a theme.
- Edit the domain/path for an existing site on the network.
We briefly discussed the possible need for validating domains and paths that will arise from #22383 efforts. We need to gather a list of tickets that could benefit.
And we just touched on how we might start working toward a future site switcher for core. This is something that would be excellent as a feature plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. for a future cycle, so if you’re interested—please speak up. Ideas are fun to pass around at this point.
Finally, I’m on the hook for ticket Created for both bug reports and feature development on the bug tracker. gathering before next week’s office hours so that we can start to prioritize a list of UI (and other) improvements. At the same time, we’ll start finding more and more to fix from the viz-rec process and from general admin UI improvements.
I’ll start that list of tickets in the comments here and then repackage it in a post for next week. Please add any tickets to the comments that you see as useful for network admin UI improvements.
Thanks to everyone for participating!