Title: Dev Chat Summary, May 10, 2023 Author: Brian Alexander Published: May 11, 2023 --- [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 11:13 pm _on_ May 11, 2023 Tags: [6-3 ( 70 )](https://make.wordpress.org/core/tag/6-3/), [6.2 ( 90 )](https://make.wordpress.org/core/tag/6-2/), [dev chat ( 932 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [PHP 8.0 ( 6 )](https://make.wordpress.org/core/tag/php-8-0/), [summary ( 980 )](https://make.wordpress.org/core/tag/summary/)    # Dev Chat Summary, May 10, 2023 The WordPress Developers Chat meeting took place on [May 10, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230510T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1683748821238729) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). * Today’s agenda: [Dev Chat agenda, May 10, 2023](https://make.wordpress.org/core/2023/05/09/dev-chat-agenda-may-10-2023/), courtesy [@webcommsat](https://profiles.wordpress.org/webcommsat/). * Last meeting summary: [Dev Chat Summary, May 3, 2023](https://make.wordpress.org/core/2023/05/03/dev-chat-summary-may-3-2023/). ## Highlighted Posts * [A Week in Core, May 8, 2023](https://make.wordpress.org/core/2023/05/09/a-week-in-core-may-8-2023/): Thank you, [@audrasjb](https://profiles.wordpress.org/audrasjb/)! > Here’s an overview of updates in TracTrac An open source project by Edgewall Software > that serves as a bug tracker and project management tool for WordPress. between > May 1 and May 8, 2023: > * 24 commits > * 56 contributors > * 46 tickets created > * 9 tickets reopened > * 49 tickets closed > * and **5 new contributors** in this period 🎉 Welcome! * [What’s new for developers? (May 2023)](https://developer.wordpress.org/news/2023/05/whats-new-for-developers-may-2023/): Check out this nifty guide to some of the latest WordPress updates, especially suited for extenders or contributors who would like to learn more about developing with WordPress. * [WP Briefing: Episode 55: Happy Anniversary, WordPress!](https://wordpress.org/news/2023/05/episode-55-happy-anniversary-wordpress/): Take a look back on the past **20 years** and how the open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. community has grown WordPress into what it is today. * [What’s new in Gutenberg 15.7? (03 May)](https://make.wordpress.org/core/2023/05/04/whats-new-in-gutenberg-15-7-03-may/): This is of the best places to see what’s new in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost- based plugin from a third-party., as well as what’s in store for the future of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. * [@webcommsat](https://profiles.wordpress.org/webcommsat/) shared: It is day two of the “#WP20 From Blogs to Blocks” campaign. We have had a request from [#marketing](https://wordpress.slack.com/archives/C0GKJ7TFA) to highlight this in [#core](https://wordpress.slack.com/archives/C02RQBWTW) and encourage more devs to take part too: [https://github.com/WordPress/Marketing-Team/issues/220](https://github.com/WordPress/Marketing-Team/issues/220). ## Release Updates * [WordPress 6.2.1 RC1 is now available](https://make.wordpress.org/core/2023/05/09/wordpress-6-2-1-rc1-is-now-available/): Help test this first minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. candidate (RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/?output_format=md#alpha-beta).) for 6.2 before next week’s final release. See the post for details on what’s been fixed, and watch the [#6-2-release-leads](https://wordpress.slack.com/archives/C04JZ199XPG) channel for additional updates. * And a reminder, for those who haven’t [submitted feedback](https://docs.google.com/forms/d/e/1FAIpQLSetmM1TctizUuo77LjcUeeqWR0mBGg_FIsiWiXXYYICvxU1Ag/viewform?usp=sharing) for the [WP 6.2 release retrospective](https://make.wordpress.org/core/2023/04/14/wordpress-6-2-dolphy-retrospective/)— [@priethor](https://profiles.wordpress.org/priethor/) has noted that the original survey deadline has been extended, so please make sure to take this opportunity to help improve future releases! ## Maintainers: Component Help Requests [@oglekler](https://profiles.wordpress.org/oglekler/) indicated a draft 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. was ready, and requested contributor involvement with [#23348: Add a “Contribute” tab to the about page](https://core.trac.wordpress.org/ticket/23348). [@audrasjb](https://profiles.wordpress.org/audrasjb/) agreed with the proposed update, but had a question about some of the languages included in the language options. Olga clarified that those were included in mobile apps, but that clarity was needed to avoid this appearing as a mistake. ## Open Floor ### PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.x Compatibility [@xavivars](https://profiles.wordpress.org/xavivars/) asked about PHP supported versions, and documentation surrounding it. He pointed out misconceptions that WordPress wouldn’t work under PHP 8.x [due to its “beta support” label](https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/), and has only upgraded his sites from PHP 7.4 recently due to this misunderstanding. He then posed these questions (paraphrased): 1. How can the PHP versions documentation page better convey that WordPress does work under PHP 8.x without major issues? 2. What are the tickets that can help move PHP 8.x support forward, and allow removal of the “betaBeta 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. support” tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems.( Not to be confused with post tags.)? 3. Do others think this is a problem? [@oglekler](https://profiles.wordpress.org/oglekler/) related the numerous PHP notices encountered when trying out WooCommerce and PHP 8.2, noting that even if WordPress was almost ready, plugins and themes still posed a challenge. [@azaozz](https://profiles.wordpress.org/azaozz/) agreed that Core functions pretty well up to 8.2, and that plugins were the main reason behind the lack of full support. [@clorith](https://profiles.wordpress.org/clorith/) added that while Core should not have fatal errors, that the deprecation notices it might throw would be indiscernible from plugin errors to most users. [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) shared two relevant discussions from last month: * [https://wordpress.slack.com/archives/C02RQBWTW/p1680727533581459](https://wordpress.slack.com/archives/C02RQBWTW/p1680727533581459) * [https://wordpress.slack.com/archives/C02RQBWTW/p168072768559110](https://wordpress.slack.com/archives/C02RQBWTW/p1680727685591109) [@joemcgill](https://profiles.wordpress.org/joemcgill/) asked if the proposal mentioned in the second link was ever published, and if there was enough support to help make it happen. While not published yet, [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) confirmed the post is still planned, and that support for the compatibility strategy has been positive. She also noted that lifting PHP 8.0’s “beta support” label was a target for WordPress 6.3. [@clorith](https://profiles.wordpress.org/clorith/) suggested that the best place to continue discussion would be the [#core-php](https://wordpress.slack.com/archives/C60K3MP2Q) channel. [@azaozz](https://profiles.wordpress.org/azaozz/) noted that the [PHP Compatibility Checker](https://wordpress.org/plugins/php-compatibility-checker/) plugin only supports up to PHP 7.4, and questioned if it could be upgraded to support newer PHP versions. [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) mentioned the relevance of the [Tide project](https://wptide.org/), and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) confirmed that Tide powers the recently updated PHP Compatibility Checker plugin. He added, however, that Tide in turn relies on [PHPCompatibilityWP](https://github.com/PHPCompatibility/PHPCompatibilityWP), which does not yet support PHP 8.x, and shared [a discussion link](https://wordpress.slack.com/archives/C7TK8FBUJ/p1680631652793589) toward adding PHP 8.x support. To help address [@xavivars](https://profiles.wordpress.org/xavivars/)‘s second question, [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) shared links to PHP 8 items in the 6.3 milestone: * [#57837 – PHP 8.x: various compatibility fixes for WordPress 6.3](https://core.trac.wordpress.org/ticket/57837)( epic tracking ticketticket Created for both bug reports and feature development on the bug tracker.) * [WordPress 6.3 PHP 8.0 Open Tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~php8+-php81+-php82&milestone=6.3&order=priority) * [WordPress 6.3 PHP 8.1 Open Tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~php81&milestone=6.3&order=priority) * [WordPress 6.3 PHP 8.2 Open Tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~php82&milestone=6.3&order=priority) [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) also pointed at a related topic that might help move PHP support-related discussions forward: [#57345: Bump the minimum required PHP version to 7.2](https://core.trac.wordpress.org/ticket/57345). [@webcommsat](https://profiles.wordpress.org/webcommsat/) indicated a possible need for [#marketing](https://wordpress.slack.com/archives/C0GKJ7TFA) team support to facilitate this work, which was confirmed by [@sereedmedia](https://profiles.wordpress.org/sereedmedia/). ### Update Error Messages [@pbiron](https://profiles.wordpress.org/pbiron/) raised the following ticket, [#57999: Don’t show error message when there is nothing to update](https://core.trac.wordpress.org/ticket/57999), requesting patch testing and design feedback. He asked if the idea of the ticket was sound, and which of the proposed patches would be preferred. [@oglekler](https://profiles.wordpress.org/oglekler/) suggested adding screenshots for the proposed patches. [@presskopp](https://profiles.wordpress.org/presskopp/) added screenshots of existing Core behavior, and [@pbiron](https://profiles.wordpress.org/pbiron/) additionally requested before/after shots for each of the patches. [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) also suggested pinging the [#design](https://wordpress.slack.com/archives/C02S78ZAL) channel for awareness. ### Screen Options and Help Panel Modernization [@oglekler](https://profiles.wordpress.org/oglekler/) asked for attention to be drawn to [#21583: Improve discoverability and visual design of Screen Options and Help Panels](https://core.trac.wordpress.org/ticket/21583), and remarked that modernizing these panels would also benefit accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility). [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) referred to [@joedolson](https://profiles.wordpress.org/joedolson/) previously [suggesting some shared UI relevance](https://core.trac.wordpress.org/ticket/21583#comment:62) between this ticket and [WP Features Notifications](https://github.com/WordPress/wp-feature-notifications), and asked if there had been any discussion about this. [@oglekler](https://profiles.wordpress.org/oglekler/) asked how these were related. Brian provided the link to a recent [Notifications feature post](https://make.wordpress.org/core/2023/04/25/wp-feature-notifications-2023-status-update/), noting that the maintainers should be able to help answer questions. Joe further clarified that the Notifications feature is looking to add another panel in the same vicinity as Screen Options/Help, and called for holistic consideration of how each of these are implemented. Before moving to the next item, [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) pointed out that because Design Team time is often limited, addressing these related WP adminadmin (and super admin) UIUI User interface concerns at the same time could be a worthwhile collaboration. ### “Roll Back” UI String [@kebbet](https://profiles.wordpress.org/kebbet/) requested feedback and 6.3 milestone consideration for ticket [#58282: Change wording where `roll back` is used](https://core.trac.wordpress.org/ticket/58282), asking if more user-friendly terms should be considered. There were several positive emoji reactions to the ticket, and [@audrasjb](https://profiles.wordpress.org/audrasjb/) swiftly added it to the 6.3 milestone. ## Next Meeting The next meeting will be on [May 17, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230517T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). _Props [@audrasjb](https://profiles.wordpress.org/audrasjb/) and [@xavivars](https://profiles.wordpress.org/xavivars/) for peer review of this summary, and to everyone who participated in the Dev Chat._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-2](https://make.wordpress.org/core/tag/6-2/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#php-8-0](https://make.wordpress.org/core/tag/php-8-0/), [#summary](https://make.wordpress.org/core/tag/summary/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/?share=bluesky) * [ X ](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/?share=x) * [ Facebook ](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/86a40c321ab5bdc2d91ea37a21d6fcee577bdc9f25b5ccfb032b18c1c237bd83? s=32&d=mm&r=g) 2. [David E. Smith](https://profiles.wordpress.org/desmith/) 3:04 pm _on_ May 12, 2023 3. It’s not clear to me whether the [compatibility matrix](https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/) is intended to convey whether “WP coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is compatible with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher x.y” or “WP core, and some subset of the most popular plugins, are compatible with PHP x.y”. I assumed the former, but the discussion above seems to imply the latter. 4. I would argue that WP core’s first responsibility is WP core, and if core is compatible( functional, passes tests, few to no warnings/deprecations being logged), then . org can and should say “WP x.y is compatible with PHP x.y”. That page can (should?) be more explicit about how WP core compatibility doesn’t imply that any given pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. or theme also is compatible. IMO the fact that there is currently _no_ combination of WordPress core and PHP, that is supported by both sides, is a bit embarrassing. 5. (I know there are edge cases for the PHP side, third-parties that provide extended support; for this purpose I’m prioritizing the PHP community over them, primarily because most of those third-parties are non-free-as-in-beer.) 6. ![](https://secure.gravatar.com/avatar/807c709d4142e246c32a82d4f675a7d88ada930e468525567a32806e0746e870? s=32&d=mm&r=g) 7. [titsmaker](https://profiles.wordpress.org/titsmaker/) 7:19 am _on_ May 13, 2023 8. AFAIK there’s still no decision on lifting minimum PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version because “millions of WP users will be left behind” at least this is my impression from reading the discussion in ticketticket Created for both bug reports and feature development on the bug tracker. 57345. So the question is do we have the stats for particular WP version used by those who are still on PHP 5.x? My guess is that in reality the number of “left behind” would be really small as 90% of people using PHP 5.x most probably do not update their sites at all. So it would be interesting to get some data to prove this right or wrong. Comments are closed. # Post navigation [← Developer blog meeting summary: May 4, 2023](https://make.wordpress.org/core/2023/05/11/developer-blog-meeting-summary-may-4-2023/) [Editor chat summary: May 10th, 2023 →](https://make.wordpress.org/core/2023/05/15/editor-chat-summary-may-10th-2023/)