Following last week’s discussion in #core-multisite (read the recap) this week’s office hours agenda was to continue the chat about the 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-related enhancements for the REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. users endpoint, focussing heavily on how to access the required functionality. Here is a wrap-up of the discussion.
Chat log in #core-multisite
Attendees: @jeremyfelt, @jnylen, @nerrad, @ipstenu, @earnjam, @kenshino, @maximeculea, @mikelking, @lukecavanagh, @flixos90
Now that the way on how one should be able to modify user roles per site was clarified last week, this week the focus laid on where one should be able to perform those actions. The current state of the
wp-json/wp/v2/users endpoint in multisite is:
- The users overview accessible with a
GET request to
wp-json/wp/v2/users only lists users that are part of the current site.
- When creating a user with a
POST request to
wp-json/wp/v2/users, that user is created and added to the current site. When providing the
roles parameter, the passed roles are added to the user, otherwise the user will still be part of the site, but without any role. See #38526 for background.
- It is possible to both read and edit any user from any site with a request to
wp-json/wp/v2/users/<id>, regardless of whether the user is part of that site.
DELETE request to
wp-json/wp/v2/users/<id> results in an error. See #38962 for background.
After the discussion about how to be able to add a specific user to a site, update their site capabilities and remove them from a site, this week’s chat revolved around where these actions can be accessed, as they are for the most part network (versus site, blog)-specific actions not available to a site administrator. The approach that was agreed on is:
- The users overview at
wp-json/wp/v2/users should continue to only show users of that site by default, but a request like
wp-json/wp/v2/users?global=true should show all users in the WordPress setup. This parameter must only be available to network administrators though, more specifically users with the
manage_network_users capability. In the future a
network parameter might also be introduced for support of multi networks, but at this point core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. does not support querying users per network. Accessing global users should be available from all sites in a setup instead of only from the main site. While this approach makes these endpoints duplicates of each other, it has several benefits like preventing the requirement for cross-domain requests, allowing easier API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. discovery and not requiring the main site of a setup to be exposed to REST API calls to a sub site.
- Assigning an existing user to a site and removing a user from a site should generally be only available to network administrators, and the site administrators of the site that is being interacted with.
- Similarly, editing a user that does not belong to the current site should only be possible for a network administrator. Currently this is available to site administrators as well which is probably wrong.
- Deleting any user completely should only be available to a network administrator. A good way to handle the
reassign parameter needs to be found though.
Before coming to the conclusion that dealing with multisite functionality at the existing users endpoint, the possibility of introducing a multisite-specific endpoint only available on the main site was discussed. However this was considered not practical due to the nature of how users work in WordPress. Having separate endpoints for other network-wide functionality might still be a possibility though as long as that component solely affects the network admin (and super admin), so this idea is something to keep in mind for thought about further network functionality endpoints in the future.
Back to the users endpoint, one related question that came up is:
- Should the sites a user belongs to be available at the
wp-json/wp/v2/users endpoint or at a future
wp-json/wp/v2/sites endpoint? If they were available in the
wp-json/wp/v2/users endpoint, every user entity would have a new sites key available if the current user had sufficient permissions to see these. If they were available in the
wp-json/wp/v2/sites endpoint, that endpoint could easily support this functionality through usage of a
@jeremyfelt suggested to look at the “Add New User” screen in the site admin to have a good use-case for how to scaffold the multisite functionality of the API endpoint. This has helped during this week’s office-hours and can also be beneficial in the future. Eventually this screen should be revamped entirely, being powered by the REST API.
Regarding the enhancements of the users endpoint, a general ticket Created for both bug reports and feature development on the bug tracker. for this task was opened at #39544. This ticket is meant to be used for discussion on the topic, while separate smaller tickets should be opened for actually implementing the individual pieces. For now feedback is welcome on that ticket. The discussion on multisite improvements for the REST API will continue at Tuesday 17:00 UTC.
/cc @rmccue and @kadamwhite