Title: forums – Make WordPress Core --- # Tag Archives: forums [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 9:33 pm _on_ May 19, 2023 Tags: [6-3 ( 70 )](https://make.wordpress.org/core/tag/6-3/), [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [6.2.1 ( 3 )](https://make.wordpress.org/core/tag/6-2-1/), [dev chat ( 932 )](https://make.wordpress.org/core/tag/dev-chat/), forums, [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 980 )](https://make.wordpress.org/core/tag/summary/), [WCEU ( 6 )](https://make.wordpress.org/core/tag/wceu/) # 󠀁[Dev Chat Summary, May 17, 2023](https://make.wordpress.org/core/2023/05/19/dev-chat-summary-may-17-2023/)󠁿 The WordPress Developers Chat meeting took place on [ 2023-05-17 at 20:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230517T2000) 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/), facilitated by [@webcommsat](https://profiles.wordpress.org/webcommsat/). * [Dev Chat Agenda May 10, 2023](https://make.wordpress.org/core/2023/05/16/dev-chat-agenda-may-17-2023/), courtesy [@webcommsat](https://profiles.wordpress.org/webcommsat/). * Last meeting summary: [Dev Chat Summary, May 10, 2023](https://make.wordpress.org/core/2023/05/11/dev-chat-summary-may-10-2023/). ## Announcements * [WordPress 6.2.1 Maintenance and Security Release](https://wordpress.org/news/2023/05/wordpress-6-2-1-maintenance-security-release/) went live on May 16, 2023. Thank you everyone who helped make this happen! ## Highlighted Posts * [Proposal: Retiring Older Default Themes](https://make.wordpress.org/core/2023/05/16/proposal-retiring-older-default-themes/): This post summarizes the current state of bundled themes in WordPress before proposes new support states for bundled themes. It also raises two potential ways to decrease the total number of themes receiving regular updates. Thanks to [@desrosj](https://profiles.wordpress.org/desrosj/) and everyone who contributed to this post. * [Command Center: Request for feedback](https://make.wordpress.org/core/2023/05/17/command-center-request-for-feedback/): Check it out and give your feedback on the UXUX User experience and APIAPI 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. for this feature. ## Release Updates The next major releasemajor release A release, identified by the first two numbers( 3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. is 6.3. ### 6.2.1 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. Discussion [@audrasjb](https://profiles.wordpress.org/audrasjb/) provided a summary of the recent 6.2.1 release, which included security patches from 4.1.x through 6.2. One fix in particular led to an issue with utilizing shortcodes in templates. The problem was being actively discussed by the Security Editor team, who began plans for a quick follow-up 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. to address the issue. See this related ticketticket Created for both bug reports and feature development on the bug tracker.: [#58333: WordPress 6.2.1 Shortcodes some shortcode no longer works!](https://core.trac.wordpress.org/ticket/58333). [@nekojonez](https://profiles.wordpress.org/nekojonez/) indicated that the issue only happens with FSE themes, confirming that their non-FSE themes were unaffected. [@audrasjb](https://profiles.wordpress.org/audrasjb/) agreed that it only affected template blocks [used in FSE themes]. [@pbiron](https://profiles.wordpress.org/pbiron/) added that shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. blocks used in blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. theme template parts remained functional. [@nekojonez](https://profiles.wordpress.org/nekojonez/) also mentioned concern that the new issue may cause users and members of the WordPress community to get the impression that shortcodes would no longer be supported, and referenced a discussion in [#forums](https://make.wordpress.org/core/tag/forums/) that could be taken out of context in support of this misunderstanding. [@ipstenu](https://profiles.wordpress.org/ipstenu/) provided a link to the [discussion](https://wordpress.slack.com/archives/C02RQC6RW/p1684277630734209), and indicated that this was a breaking change that did not include a notification to users beforehand. She suggested that the [release post](https://wordpress.org/news/2023/05/wordpress-6-2-1-maintenance-security-release/) could have been more clear as to why shortcode support in block templates was removed. [@nekojonez](https://profiles.wordpress.org/nekojonez/) expressed agreement about wishing for more clarity in the post. [@nekojonez](https://profiles.wordpress.org/nekojonez/) noted that workarounds existed for the issue, and might be shared with clear “use as your own risk” language. [@pbiron](https://profiles.wordpress.org/pbiron/) explained that one of the options was to move the shortcode block into a template part, and for the template part to replace the original shortcode block used in the template. He added [a comment to the ticket](https://core.trac.wordpress.org/ticket/58333#comment:41) explaining this. [@webcommsat](https://profiles.wordpress.org/webcommsat/) asked [@audrasjb](https://profiles.wordpress.org/audrasjb/) if the post could be updated with information about the workaround. [@azaozz](https://profiles.wordpress.org/azaozz/) asked if the workarounds “revert” the security fix, and [@audrasjb](https://profiles.wordpress.org/audrasjb/) confirmed that yes, they rewrite the logic and re-introduce the security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have.. [@psdtohtmlguru](https://profiles.wordpress.org/psdtohtmlguru/) indicated that 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.-based workaround impacted performance on complex templates, and asked for a link to the security fix ticket. [@audrasjb](https://profiles.wordpress.org/audrasjb/) shared a link to the commit, but pointed out the ticket was in Hackerone and not visible to the public. [@francina](https://profiles.wordpress.org/francina/) also noted that security fixes are not disclosed publicly, and JB provided a supporting link to the [Core Handbook’s security FAQ](https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/). [@nekojonez](https://profiles.wordpress.org/nekojonez/) expressed worry that not knowing details of the security flaw may put into question the safety of non-FSE theme shortcode use, and asked for more communication on it. [@pbiron](https://profiles.wordpress.org/pbiron/) added that it was strange the vulnerability would affect shortcode usage directly in a template, but not in a template part of post content. [@ndiego](https://profiles.wordpress.org/ndiego/) asked if anyone could share why shortcodes behaved differently between these usages, and [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/) suggested the discussion was getting too deep for now. [@psdtohtmlguru](https://profiles.wordpress.org/psdtohtmlguru/) asked for confirmation that shortcodes in templates don’t work, but that shortcodes in post content would continue to work. [@nekojonez](https://profiles.wordpress.org/nekojonez/) indicated the need to await further updates from the security and editor teams, suggesting a clarification post in the meantime. [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/) agreed, with Timothy suggesting the post primarily clarify that the security team is aware of and discussing solutions to the issue. [@azaozz](https://profiles.wordpress.org/azaozz/) recommended that shortcodes should not be used in templates, due to performance issues on top of the security concerns. Several attendees responded [in the thread](https://wordpress.slack.com/archives/C02RQBWTW/p1684355604343709) explaining that shortcodes were beneficial for numerous reasons, and [@asafm7](https://profiles.wordpress.org/asafm7/) shared their particular use case. _[Editor’s Summary: From this long thread the impression is that regardless of security or performance implications, shortcodes are currently a valuable content mechanism that does not yet have a clear replacement for all use cases.]_ ### 6.4 Q&A [@francina](https://profiles.wordpress.org/francina/) asked for an informal Q&A session around WordPress 6.4, details of which can be found in [this Slack thread](https://wordpress.slack.com/archives/C051Z1SKBDZ/p1683910470357619). [@karmatosed](https://profiles.wordpress.org/karmatosed/) asked if there was a list of questions for the call, to provide preparation time to address them. [@estelaris](https://profiles.wordpress.org/estelaris/) responded with a link to the spreadsheet ([see comment](https://wordpress.slack.com/archives/C02RQBWTW/p1684355836194789)) where more questions could be added. Francesca clarified that the Q&A would be informal and occur on Zoom. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) asked about the possibility of two sessions to accommodate timezone differences, the idea which was seconded by Tammie. Francesca agreed to make the calls more formal, and to post about it in make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. ## Maintainers: Component Help Requests ### wp.zip Domain [@francina](https://profiles.wordpress.org/francina/) proposed that the https:// wp.zip domain redirect to the latest WordPress release ZIP file — [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) asked if [https://wordpress.org/latest.zip](https://wordpress.org/latest.zip) was the suggestion — rather than the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) homepage where it currently leads. [@pbiron](https://profiles.wordpress.org/pbiron/) suggested opening a ticket in [Meta Trac](https://meta.trac.wordpress.org), and proposed that [https://wordpress.org/download/](https://wordpress.org/download/) might be preferable to avoid user confusion/concern that might result from a link leading to an automatic download. [@webcommsat](https://profiles.wordpress.org/webcommsat/) agreed that avoiding automatic downloads would be better for 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). ### 6.3 Tickets [@oglekler](https://profiles.wordpress.org/oglekler/) shared two tickets that could be moved into the 6.3 milestone, which had been tested: * [#31635: Bulk Edit -> Publish should publish scheduled posts](https://core.trac.wordpress.org/ticket/31635) * [#57947: Publishing draft posts via Bulk Edit should publish them with the current date](https://core.trac.wordpress.org/ticket/57947) [@webcommsat](https://profiles.wordpress.org/webcommsat/) called for help testing the patches, and reiterated adding test results to tickets for visibility. ## Open Floor ### WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. 󠀁[Learn more](https://central.wordcamp.org/about/)󠁿. Europe 2023 [@webcommsat](https://profiles.wordpress.org/webcommsat/) called for updating Core and Core Test information for Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/), thanking [@estelaris](https://profiles.wordpress.org/estelaris/) for gathering the info. Estela emphasized the need to email the info to first-time contributors by Friday, 19 May. [@webcommsat](https://profiles.wordpress.org/webcommsat/) also asked for volunteers to facilitate the Core tables at the event. Both [@oglekler](https://profiles.wordpress.org/oglekler/) and [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) expressed interest. [@webcommsat](https://profiles.wordpress.org/webcommsat/) asked [@estelaris](https://profiles.wordpress.org/estelaris/) if there was to be a table to assist contributors in setting up local environments, noting that a dedicated table has worked well before. Estela confirmed there would be a table, but that emails to first-time contributors could help ensure they are better prepared, particularly with software downloads. [@webcommsat](https://profiles.wordpress.org/webcommsat/) also noted the emails could include the date/time for upcoming new contributor meetings. [@webcommsat](https://profiles.wordpress.org/webcommsat/) said they were reviewing Contributor Day info from WC Asia that should be added to the Core Handbook, noting that it was also being added to the Make Teams introduction document ([link provided by @estelaris](https://wordpress.slack.com/archives/C02RQBWTW/p1684357115121639)). [@webcommsat](https://profiles.wordpress.org/webcommsat/) asked that Contributor Day attendees share in this post’s comments if they would be able to help at a Core table. [@estelaris](https://profiles.wordpress.org/estelaris/) indicated that there would be approximately six tables dedicated to the Core team, and [@desrosj](https://profiles.wordpress.org/desrosj/) asked which Core focus area had been identified for each table. Estela referred to the introduction document, and that nothing in particular had been mentioned. Jonathan would review the document and try to find other teams to collaborate with. Finally, [@webcommsat](https://profiles.wordpress.org/webcommsat/) noted that tickets were still available for both the conference and Contributor Day. ## Next Meeting The next meeting will be on [May 24, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230524T2000). 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 [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) for co- authoring and [@audrasjb](https://profiles.wordpress.org/audrasjb/) for peer review of this summary._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#6-2-1](https://make.wordpress.org/core/tag/6-2-1/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/), [#wceu](https://make.wordpress.org/core/tag/wceu/) [ ](https://profiles.wordpress.org/schlessera/) [Alain Schlesser](https://profiles.wordpress.org/schlessera/) 9:04 am _on_ January 11, 2019 Tags: [core-php ( 68 )](https://make.wordpress.org/core/tag/core-php/), forums, [hosting ( 57 )](https://make.wordpress.org/core/tag/hosting/), [marketing ( 6 )](https://make.wordpress.org/core/tag/marketing/), [meta ( 41 )](https://make.wordpress.org/core/tag/meta/), [plugins ( 33 )](https://make.wordpress.org/core/tag/plugins/), [polyglots ( 6 )](https://make.wordpress.org/core/tag/polyglots/), recap, [servehappy ( 31 )](https://make.wordpress.org/core/tag/servehappy/), [themes ( 43 )](https://make.wordpress.org/core/tag/themes/), [wcus ( 6 )](https://make.wordpress.org/core/tag/wcus/) # 󠀁[Site Health Check Project review at WCUS](https://make.wordpress.org/core/2019/01/11/site-health-check-project-review-at-wcus/)󠁿 _This is a verbose set of notes to record the discussions that took place at WCUS and to reflect the work that has been done across multiple teams._ The Site Health Check project is a collaborative multi-team project with a focus on encouraging better site maintenance. This project benefits not just WordPress users, but also the surrounding PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher ecosystem as a whole. Our hope is that this will prompt a lot of PHP updates across the web. It started as a project to focus efforts on getting users to update their hosting version of PHP from 5.2 to something where the End of Life has not already passed. The project was initially called ServeHappy, homage to the BrowseHappy project which was a global tech effort to move away from Internet Explorer 6. The problem with the project name was that, when tested with users who did not know about the ins and outs of the project, the name was confusing and was not clear what the project’s intentions were. The project is now known as the **Site Health Check project**. It encourages and hints to users that if they run a website, they should have a routine of checking and updating not just WordPress but underlying technologies that the site is built on. It also builds positive website ownership and habits. The project is split into what can be considered 3 parts – changes to WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself, a site health check 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. and the site health check community support. ## Upcoming changes to WordPress Core The core-centric side of the project still reflects the Servehappy origins. This includes: * An **information page** on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) explaining the importance of updating PHP. The team has been working on improving the language used to benefit non-technical people and have clear instructions of what to do if they find out their site is running an old version of PHP. * A **dashboard notice** that will inform users if their site is running on a PHP version that WordPress considers outdated and plans to drop support for in a future update. - The version shown in the dashboard is APIAPI 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.-driven which means that WordPress leadership has a centralized “knob” to tune the PHP version distribution. - The dashboard includes a link to wordpress.org/support/update-php which has generic information on what the notice means and how to update PHP on their servers. * There will be an environment variable or a filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/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. which allows hosting companies to modify the link to the “Update PHP” page on their servers so that it goes to something more relevant for their customers. - There are some concerns of security problems and abuse over the link redirection. * The team has been working on a feature to add **white screen protection**, which the hosting group felt was helpful and cool. The white screen protection catches any fatal errors that a PHP update might produce. From the front facing side of the website, the site will still be white screened, but with the protection in place, the user can still access the adminadmin (and super admin) panel. * There was a discussion whether it would be better for the site to be slightly broken rather than completely broken, but the general consensus was that it is better to white screen because from the Core Team perspective, they cannot be sure of what the PHP error causes, and thus can’t be sure that all the information being shown is meant to be public. It is better to white screen the whole website but ensure that access to the admin panel is still accessible. Once logged in, there will be a general notification regarding the WSOD. ### PHP minimum required headers #### Plugins For a while, WordPress plugins have been able to [set a minimum PHP required comment](https://make.wordpress.org/plugins/2017/08/29/minimum-php-version-requirement/) as part of the plugin headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.. To date it has not done anything but set the intention that the plugin author is able to declare what PHP minimum version they are willing to support. Work is being done so that the Add New Plugin admin screen will show all plugins a user searches for, but will not be able to install any plugins that require a newer version of PHP without updating that first. Another task being worked on is blocking plugin updates if the newer version requires a higher version of PHP, same as it currently works if the update requires a higher version of WordPress. This gives plugin authors better control of what PHP versions they are willing to support, and will hopefully encourage people to upgrade their version of PHP at the same time. This change will allow plugin authors the choice to use more modern PHP functionality and syntax without worrying their plugin will break for the end user. #### Themes For themes, the `Requires PHP` header is not implemented yet, as they didn’t have the same `readme.txt` file up until recently: [https://make.wordpress.org/themes/2018/10/25/october-23rd-theme-review-team-meeting-summary/](https://make.wordpress.org/themes/2018/10/25/october-23rd-theme-review-team-meeting-summary/) Now that new themes do have that requirement, there is an expectation that the header will be implemented as well in the foreseeable future. Here’s a ticketticket Created for both bug reports and feature development on the bug tracker. for that: [#meta-3718](https://meta.trac.wordpress.org/ticket/3718) #### Relevant TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Tickets * [#43986](https://core.trac.wordpress.org/ticket/43986) Disable “Install Plugin” button for PHP required version mismatch. This has already been committed to core. * [#43987](https://core.trac.wordpress.org/ticket/43987) BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. plugin updates if required PHP version is not supported – Plugins screen * [#44350](https://core.trac.wordpress.org/ticket/44350) Block plugin updates if required PHP version is not supported – Updates screen The latter two trac tickets are currently slated for 5.1 as well, planned for February 21: [https://make.wordpress.org/core/5-1/](https://make.wordpress.org/core/5-1/) The feature merge deadline is January 10 though, so it needs to be discussed at the next [#core-php](https://wordpress.slack.com/messages/C60K3MP2Q) meeting whether making it into 5.1 is still feasible. A prerequisite for these changes is the WSOD protection that needs to be completed and committed by the deadline: [#44458](https://core.trac.wordpress.org/ticket/44458) #### Join in The group has weekly meetings on Mondays 16:00 UTC on in the [#core-php](https://wordpress.slack.com/messages/C60K3MP2Q) channel of WordPress 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/). GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/): [https://github.com/WordPress/servehappy](https://github.com/WordPress/servehappy) ## Site Health Check Plugin The site health check plugin is a way for users to be able to see technical details of their website setup without going into the server side of things. It is useful to conducting top level investigation work without accessing the server directly. 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. version of the plugin takes the best practices from the Hosting Team’s documentation and checks the server against that. This includes: WordPress version number, plugins and themes are up to date, PHP version number, if HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. is active across the whole site as well as a number of other things. When Health Check gives notifications about upgrading things, it hands users off to plain English documentation to walk them through the process. For example: [https://wordpress.org/support/update-php/](https://wordpress.org/support/upgrade-php/). Notifications for plugins and themes being up to date are based on the version inside the plugin and theme repo. If a theme or plugin is not present in the repo, it will assume it is up to date and will not give an error. Eventually, a lot of the Site Health Check plugin will be in core. The Site Health Check Plugin uses a traffic light system to flag up the importance of a suggested change. The definition of critical vs non-critical update notifications is from a security perspective. If it is a security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have., it’s critical. Early user testing with the community has shown that the plugin suffers from a lack of designer eye. During WCUS, we have had a designer volunteer to review the interface and give feedback. This should help with the usability of the plugin and balance it between positive reinforcement of things that are set up as guided by best practices whilst not over- burdening people with extra technical information. There is some useful documentation on how to use the Site Health Check Plugin: [https://make.wordpress.org/support/handbook/appendix/troubleshooting-using-the-health-check/](https://make.wordpress.org/support/handbook/appendix/troubleshooting-using-the-health-check/) #### Join in – Github: [https://github.com/wordpress/health-check](https://github.com/wordpress/health-check) – WP.org : [https://wordpress.org/plugins/health-check](https://wordpress.org/plugins/health-check) ## Site Health Check Desks & Community Support In-person support is invaluable. When a user is unsure of what to do, they can find in-person support at their local meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. and WordCamps. To omit any surprises, we can encourage our community to pre-warn and prepare as many people as possible. The idea of Site Health Check desks has been tested in 3 different WordCamps and 1 meet-up with improvements and suggestions being fed back to the plugin and fliers. Site Health Checks is an extension of the Happiness Bar, and by asking the simple question “Do you know what version of PHP your website is running?”, people either: * Know & it is up to date – get a high-five. Say Awesome and keep up the good work. Pre-warn the next EOL of PHP Dates. * Know & it is out of date – highlight the EOL date has already passed and recommend they update their PHP version. * If they don’t know, Check if they know how to check. If they do, suggest that they check and that they want it to be 7.2 or higher. 7.1 EOL is in a year. * If they don’t know and don’t know how to check, invite them to sit down and the volunteers can help them check using the Site Health Check plugin. DO NOT scrape the site. They can end up being blocked off the servers. Postcards were created with 5 core things to check. As well as printable table toppers. They are used as fliers for people to know where to download the site health check. Meetup organisers have also shown an interest in running the site health check and promoting it at their meet-ups. This is where much of the user testing of both the “Update PHP” information page and the Site Health Check plugin is happening. ## Plugins and Themes Plans Plugins and Themes served from WordPress.org can be automatically checked and updated to be compatible with 7.X. This is because there is access to the SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. where these plugins are being pushed from. Ideally, plugin authors who have a plugin in the plugin repo will update their plugins to be compatible with PHP 7.X. There are already plugins such as the [PHP Compatibility Checker](https://wordpress.org/plugins/php-compatibility-checker/) which people can use to check how compatible their websites are with a version of PHP. ### How are premium plugins and themes going to be handled? The plugin team at WordPress.org can contact authors, but ultimately it is up to the plugin author to action the suggestions that are made from the WordPress.org team. If there is no answer, or the author does not wish to fix errors, then this is a dead end. ## Target Dates [WordPress 5.1](https://make.wordpress.org/core/5-1/)  ->  ServeHappy notice + White Screen of Death protector WordPress 5.2 ->  Site Health Check plugin ## Where hosting companies come into play We would like hosting companies to go aggressively, pushing their communities forward before WordPress does. We know that, as a hosting company, many of you will see the same issues come up during a PHP update. It would be useful to the rest of the group if any information of any PHP errors that are being seen repeatedly and information about which plugin or theme is causing it. It will allow the rest of the team to prioritise which plugins and themes need attention to be fixed across the whole community. It will also help the support team if any solutions are found to be shared, so that they know what to be suggesting in the forums. We may be able to add notices before a PHP update into the health check which highlights problematic plugins. Hosts with PHP lower than 5.6 may see some initial notifications before that date. Hosting company teams are most likely to know other people working in the hosting sector. **Above all else – get the word out. ** Big hosts are represented well here, but as a community we are aware and worried about the smaller, independent hosters. Talk to your hosting friends. Let them know this is coming. Invite the small hosting companies to join the Hosting Team on WordPress.org for up to date information of what is upcoming and will be effecting hosters. The more we can update in batches the less burden there is across the whole industry. ## Where plugin and theme authors come into play If plugin and theme authors ensure that their plugins have a PHP minimum version set in their required header, then their plugins and themes will be ready once the PHP requirement is being enforced. Plugin and theme authors should also ensure that their plugins are compatible with PHP 7.X. Tools such as PHP Code SnifferPHP Code Sniffer [PHP Code Sniffer,](https://github.com/squizlabs/PHP_CodeSniffer) a popular tool for analyzing code quality. The [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards/) rely on PHPCS. (PHPCSPHP Code Sniffer [PHP Code Sniffer,](https://github.com/squizlabs/PHP_CodeSniffer) a popular tool for analyzing code quality. The [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards/) rely on PHPCS.) or the PHP Compatibility Checker as mentioned above should help. ## Actions from the meeting – Ensure there is communication with the hosting team regarding release date plans. –  [#core-php](https://wordpress.slack.com/messages/C60K3MP2Q) should be cross posting ServeHappy notes to the Hosting P2P2 A [free theme for WordPress](http://p2theme.com/), known for front-end posting, used by WordPress for development updates and project management. See our [main development blog](https://make.wordpress.org/core/) and [other workgroup blogs](https://make.wordpress.org/). as well. – WordPress.hosting has been taken, unsure by who. It would be handy to have WordPress. hosting symlink to Hosting Team P2 to help getting other hosting companies to join the Hosting Team – Recommend that Hosting Team check and sync up the Best Practices documentation. – Can someone from the hosting team please review and ensure that Health Check plugin is checking against everything that exists in the “Hosting Best Practices” doc. – Recommended to Health Check plugin to check out Lighthouse plugin UIUI User interface. – Write up more in-depth info for meetup and WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). organisers, have postcard and table toppers online so they can be shared and translated easily. ## Thanks The effort to raise the minimum PHP version requirement of WordPress is a big cross- team effort. Big thanks to * [@brettface](https://profiles.wordpress.org/brettface/) for the notes. * [#core-php](https://make.wordpress.org/core/tag/core-php/), [#plugins](https://make.wordpress.org/core/tag/plugins/), [#themes](https://make.wordpress.org/core/tag/themes/) and [#meta](https://make.wordpress.org/core/tag/meta/) team for their hard work * the [#hosting](https://make.wordpress.org/core/tag/hosting/) team for their input and support * [@alexdenning](https://profiles.wordpress.org/alexdenning/) from [#marketing](https://make.wordpress.org/core/tag/marketing/) team for the content review * [@clorith](https://profiles.wordpress.org/clorith/) from [#forums](https://make.wordpress.org/core/tag/forums/) for the health-check plugin development * WordCamp London 2018, WCEU 2018 and WordCamp Brighton 2018 organisers for allowing us to test the Health Check help desk concept * And to the [#polyglots](https://make.wordpress.org/core/tag/polyglots/) team who will be asked in the near future to translate our work for the whole community. [#recap](https://make.wordpress.org/core/tag/recap/), [#servehappy](https://make.wordpress.org/core/tag/servehappy/), [#wcus](https://make.wordpress.org/core/tag/wcus/)