Site Health Chat Summary: July 8th

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher Version – soft bump

Note: The soft bump is the term referring to the PHP upgrade notice widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. shown in the dashboard, and not the minimum requirement to use WordPress.

The discussion on what version to start recommending users upgrade to is going on in the comments at, but we also covered them a bit during the Hosting meeting this week.

Currently it seems the best approach would be to recommend updating to PHP 7.1 (skipping 7.0 as it’s technically not maintained any more), but we’ll leave the conversation going out the week, then make a decision on this next week. After a version has been decided on we make it known via posts to the make blogs what the intentions are, and what versions we are aiming for, and then make thew bump. This should allow hosts and developers some time to prepare for the potential support requests.

Ticketticket Created for both bug reports and feature development on the bug tracker. review

We covered a couple of tickets as well that were brought up by participants.

#47651 – This has been flagged for design feedback, as it needs a UIUI User interface/UXUX User experience perspective to help with direction and user flow.

#47644 – This has a patchpatch 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., but after some discussion it will need a refresh to help with making it a bit more friendly towards the average user.

#47321 – This had some initial discussions in the channel after the meeting, but during the meeting it was covered that it needs some copy-editing. The ticket will have the outcome of the copy-discussion added once a final decision has been made.

#46925 – The ticket is ready, but was unfortunately not reviewed yet. It will get reviewed this week, and we will hopefully be more on top of tickets now that they’re more easily categorized.

Read the meeting transcript in the Slack archives. (A Slack account is required)