This recap is a summary of our previous PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.
You can find this meeting’s chat log here.
- The meeting focused on the individual pieces that are left to complete so that the most essential Servehappy parts can become part of the WordPress 5.1 release (planned schedule has first Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. set at January 10th).
- For the fatal error recovery mechanism (see #44458 or GitHub PR for development) the following steps are needed:
- Add support for recovering errors by the theme by pausing it. It was determined before that the admin (and super admin) can work without an active theme, so implementation of this should be straightforward based on the existing code that already handles this for plugins.
- In addition to displaying a note in the frontend when an error occurs (customizable via a
php-error.php drop in), an email with the same message should be sent to the admin email address.
- @schlessera will take care of implementing these two remaining tasks.
- 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 team will furthermore have an additional look at the existing implementation of multisite support.
- A few updates are required for the Update PHP page:
- Instead of having the content coming from the editor, it should be hardcoded and displayed via a template so that translation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. of the content is more streamlined and can happen via GlotPress. Furthermore it makes it a quicker process to add visual assets to the page later. @flixos90 is taking care of this.
- The page slug needs to be changed from
update-php, as previously discussed, including a redirect. @sergeybiryukov has already completed this work.
- For the actual notice in core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself, a few tweaks need to be added.
- The version numbers need to be updated for WordPress 5.1.
- The link URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to the page needs to be updated to account for the slug change.
- The link URL needs to be customizable via both an environment variable (to be set by hosting providers) and a filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. (for later adjustments in the codebase).
- @flixos90 is working on these updates as part of #45686.
- In the Servehappy 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. endpoint, the recommended PHP version should be set to 7.3, and the lowest acceptable version should be set to 5.6 to account for the future version bump. On any version below that, WordPress users will see a warning. Furthermore the information on official PHP version support needs to be updated as both PHP 5.6 and 7.0 are no longer support (or will be in very few days). This update has as of now been committed already as well.
- During the work on the 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. changes in the aftermath of the meeting, it came up that adjusting version numbers exposed by wordpress.org should become a more straightforward process that can happen in a central location. This part is not crucial to have prior to WordPress 5.1, but is a minor tweak to make maintenance simpler in the future.
- Still left is enhancing the page content with visual assets. It was agreed that these should not contain any language-dependent text. Among the suggestions were:
- a diagram of how the server hardware, PHP, and WordPress relate to each other
- a timeline of PHP version history
- None of the attendees felt capable or had availability to work on such visual assets. If you can help with this over the next couple weeks, please let us know in the comments or the #core-php channel on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
- Due to the holidays in many parts of the world, the meetings in the next two weeks are cancelled. Finishing the features for WordPress 5.1 is a high priority though, and communication should continue asynchronously as needed. The next official meeting will take place only a few days before the intended 5.1 Beta release, so at that point everything should preferably be good to be merged.
Next week’s meeting
- Next meeting will take place on Monday, January 7th, 2019 at 16:00 UTC in #core-php.
- Agenda: Finalize remaining WordPress 5.1 work in order to be ready in time for the first Beta (Janurary 10th).
- If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account.
#php, #servehappy, #summary