Office Hours Recap
The agenda for this office hours meeting included a discussion around the introducing a
wp_blogmeta table and related
*_site_meta() functions to store arbitrary data for sites, particularly as a means to extend the future sites 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/. endpoint. See #37923 for the respective ticket Created for both bug reports and feature development on the bug tracker..
The meeting’s chat log
Attendees: @dac @earnjam @flixos90 @jeremyfelt @jjj @maximeculea @spacedmonkey @stephdau @stevenkword
- There is a feature plugin available for installing site meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. (the database table is called
blogmeta for legacy reasons).
- A consensus was reached for proposing a new
blogmeta table which will be beneficial but not required for the planned REST API sites endpoint.
- Priority for the 4.9 release will be the introduction of this new table with focus on adding a related meta_query to wp_site_query deferred to a subsequent release. See #40229.
The next office hours will take place on Tuesday 16:00 UTC. An agenda for it will be posted in advance.
Ticket Scrub Recap
The agenda for this ticket scrub was to go through 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 good-first-bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. tickets. We worked off of this report with the aim of general gardening, adjusting keywords as necessary and removing
good-first-bug keywords for tickets that are overly complex or have been open and without activity for an extended period of time.
The meeting’s chat log
Attendees: @danhgilmore @earnjam @flixos90 @pcarvalho @pmbaldha @stevenkword
- #20537: Don’t spawn cron requests for suspended blogs.
- We successfully applied the latest patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. and provided a request for user testing.
- #37799: Add progress indicator to “Upgrade Network (versus site, blog)” page
- We successfully applied the latest patch and provided UI User interface feedback.
- #39213: Audit the network pages notices.
- We successfully applied the latest patch and provided a request for user testing.
- #39419: Explicitly globalize global variables in ms-settings.php
- We successfully applied the latest patch and provided a request for documentation.
- #41167: Remove help text duplication on Site editing screens in network admin (and super admin)
- We successfully applied the latest patch and provided a request for a refreshed patch that resolved warnings from trailing CRs.
The next ticket scrub will take place on Monday 17:00 UTC. An agenda for it will be posted in advance.
If you were unable to attend one of these meetings but have feedback, please share your thoughts in the comments on this post. In case there’s a need for further discussion we will ensure to make time for it in one of next week’s chats. See you next week!