{"id":3381,"date":"2017-01-29T11:15:33","date_gmt":"2017-01-29T10:15:33","guid":{"rendered":"https:\/\/en.florianbrinkmann.de\/?p=3381"},"modified":"2020-02-09T10:59:57","modified_gmt":"2020-02-09T09:59:57","slug":"wordpress-weekly-recap-4-improving-the-settings-api-and-more","status":"publish","type":"post","link":"https:\/\/florianbrinkmann.com\/en\/wordpress-weekly-recap-4-improving-the-settings-api-and-more-3381\/","title":{"rendered":"WordPress weekly recap #4: Improving the settings API and more"},"content":{"rendered":"
The core team works on improvements for the settings API. It should become easier for developers to use the API and the accessibility of the generated markup should be improved.<\/p>\n\n\n\n\n\n\n\n
On January 2 and 16, the core team held meetings regarding the settings API. One aspect to tackle is improving the settings page\u2019s accessibility \u2014 currently, table markup is used. The other aspect is that developers have to write an own callback function even for the most basic fields. The team wants to add support for various field types, so this will not be necessary anymore.<\/p>\n\n\n\n
You can find more information about the meeting in the post \u00bbImproving the Settings API for accessibility and ease-of-use\u00ab by Felix Arntz<\/a>.<\/p>\n\n\n\n A At this moment, the REST API sites endpoint for multisite<\/h3>\n\n\n\n
\/sites\/<\/code> endpoint should meet the following requirements (quoted from Jeremy Felts post):<\/p>\n\n\n\n
\/sites\/<\/code> endpoint should provide a useful set of data for each site without requiring the use of
switch_to_blog()<\/code>.<\/li>
\/sites\/<\/code> for something other than ID, domain, and path.<\/li><\/ul>\n\n\n\n
\/sites\/<\/code> endpoint is limited to the fields from the
wp_blogs<\/code> table. Things like the site\u2019s name or description are stored in an own table for each site. Because the use of
switch_to_blog()<\/code> would be inefficient, a new table was proposed to store several data of the sites. After some discussion, these are possible data for the table:<\/p>\n\n\n\n
home<\/code><\/li>
siteurl<\/code><\/li>
blogname<\/code><\/li>
blogdescription<\/code><\/li>
admin_email<\/code><\/li><\/ul>\n\n\n\n