The REST API team had a kickoff meeting for 4.8. Besides that, the two design leads for the focus areas editor and customizer asked the community for feedback, what they would like to see in these components.<\/p>\n\n\n\n\n\n\n\n
There were two meetings regarding the REST API\u2019s user endpoints in multisite in the last two weeks. The first meeting\u2019s topic was the current state of the It should be possible to remove a user from a site with a More information about that can be found in the post \u00bbImproving the REST API users endpoint in multisite\u00ab by Jeremy<\/a>.<\/p>\n\n\n\n The main goal of this week\u2019s meeting was to define how these functions should be accessed. Among other things, the team noted that it should be possible for network administrators to get all users of a multisite through something like More on that and other considerations of the team in the post \u00bbControlling access to REST API user functionality for multisite\u00ab by Felix Arntz<\/a>.<\/p>\n\n\n\n The REST API team had a kickoff meeting for 4.8. The focus for 4.8 is going to be API usage in the backend \u2013 other areas will continue development as Feature Projects<\/em> which have to meet additional requirements. They need to have a core committer as a reviewer and a design doc with a few specifics (they will be laid out in the future, one of them is a detailed merging plan).<\/p>\n\n\n\n The team uses Trello for the organization<\/a>. The core API team is going to work a lot on JavaScript stuff and new endpoints. The Appearance<\/em> menu is the biggest area without API support \u2013 the team is going to work together with the customizer team in this area. For the frontend, Press This is a great candidate for API usage, and work is already underway in ticket #38343<\/a>. The list tables will need much work. Quick Edit and Quick Delete are a good starting point here.<\/p>\n\n\n\n You can find more information about that in the post \u00bbAPI Chat Summary: January 9th (4.8 kickoff)\u00ab by Ryan McCue<\/a>.<\/p>\n\n\n\n On January 11, the core team released the security and maintenance version WordPress 4.7.1. It fixes eight security issues and 62 bugs from 4.7. More about the new version in Aaron D. Campbell\u2019s post \u00bbWordPress 4.7.1 Security and Maintenance Release\u00ab<\/a>.<\/p>\n\n\n\n The design team published two posts to ask for feedback for tho of the three focus areas, and there have already been several comments on both of them. \u00bbWhat makes a great editor?\u00ab asks for editor feedback<\/a>, the post \u00bbWhat makes a great customization experience?\u00ab for feedback on the customizer<\/a>.<\/p>\n\n\n\n If you have an opinion on one or both areas, write a comment on the specific post.<\/p>\n\n\n\n In this week\u2019s meeting, a few final issues with the new plugin directory were covered. The current schedule is to release the new version on January 20.<\/p>\n","protected":false},"excerpt":{"rendered":" The REST API team had a kickoff meeting for 4.8. Besides that, the two design leads for the focus areas editor and customizer asked the community for feedback, what they would like to see in these components.<\/p>\n","protected":false},"author":1,"featured_media":3219,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"wpf_show_in_dewp_planet_feed":false,"flobn_post_versions":"","webmentions_disabled_pings":false,"webmentions_disabled":false,"lazy_load_responsive_images_disabled":false,"footnotes":""},"categories":[37],"tags":[116],"class_list":["post-3342","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-wordpress-weekly-recap"],"wp-worthy-pixel":{"ignored":false,"public":"c4187dda62bc4de9895a35f206295807","server":"vg01.met.vgwort.de","url":"https:\/\/vg01.met.vgwort.de\/na\/c4187dda62bc4de9895a35f206295807"},"wp-worthy-type":"normal","_links":{"self":[{"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/posts\/3342","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/comments?post=3342"}],"version-history":[{"count":3,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/posts\/3342\/revisions"}],"predecessor-version":[{"id":5924,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/posts\/3342\/revisions\/5924"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/media\/3219"}],"wp:attachment":[{"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/media?parent=3342"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/categories?post=3342"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/florianbrinkmann.com\/en\/wp-json\/wp\/v2\/tags?post=3342"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}wp-json\/wp\/v2\/<\/code>users endpoint in multisite. The team defines two tasks in the meeting (quoted from the post by Jeremy Felt):<\/p>\n\n\n\nPUT<\/code> request to the wp-json\/wp\/v2\/users\/#<\/code> endpoint.
\nIt should be possible to delete a global user with a DELETE<\/code> request to the wp-json\/wp\/v2\/users\/#<\/code> endpoint once all sites have been disassociated.<\/p>\n\n\n\nwp-json\/wp\/v2\/users?global=true<\/code>. Generally, it should only be possible to add existing users to a site or remove them for network admins or admins from the specific site.<\/p>\n\n\n\nREST API chat on January 9<\/h3>\n\n\n\n
WordPress 4.7.1<\/h3>\n\n\n\n
Misc<\/h3>\n\n\n\n
Design<\/h2>\n\n\n\n
What makes a good editor and customization experience?<\/h3>\n\n\n\n
Meta<\/h2>\n\n\n\n
New plugin directory<\/h3>\n\n\n\n