Make WordPress Core

Opened 4 weeks ago

Last modified 2 weeks ago

#46065 assigned enhancement

Add possibility to set a higher recommended php version for the "Update PHP notice"

Reported by: j-falk Owned by: flixos90
Milestone: 5.1.1 Priority: normal
Severity: normal Version: trunk
Component: General Keywords: needs-patch servehappy
Focuses: Cc:


The "Update PHP core notice" was introduced by #41191 (ticket), refined by #45686 (ticket) and the trigger to show the notice is managed by a check to a centralized WordPress api call which responds with if the current site has a insecure/outdated version of PHP.

This means that it is easy to centrally raise the minimum versions for a site to be considered unsecure or outdated.

However one addition to this that would be great is if it would be possible for a host to set a different and higher minimum than what is set centrally.

This was proposed previously at https://make.wordpress.org/core/2019/01/14/php-site-health-mechanisms-in-5-1/#comment-35240 and discussed briefly https://wordpress.slack.com/archives/C3D6T7F8Q/p1547666779187700.

Eg at the managed WP host Seravo we now have our own admin notice about upgrading a site using a PHP version below 7.0, which is implemented through a must-use plugin we install on all sites. It would be great if we, and other hosts, would have the possibility to instead do this by using the PHP update notice now in core.

The clear benefit of this would be to help hosts that are comfortable guiding their clients to update their PHP versions quicker than what WordPress centrally does.

Change History (7)

#1 @j-falk
4 weeks ago

One suggestion of how this could be implemented is to make it similar as to how the "Update PHP URL" now can be set both as an environment variable and through a filter.

This ticket was mentioned in Slack in #hosting-community by j-falk. View the logs.

4 weeks ago

#3 @mikeschroder
4 weeks ago

  • Keywords needs-patch added
  • Version set to trunk

This ticket was mentioned in Slack in #core-php by mike. View the logs.

3 weeks ago

#5 @mikeschroder
3 weeks ago

  • Keywords servehappy added

#6 @flixos90
3 weeks ago

  • Milestone changed from Awaiting Review to 5.1.1
  • Owner set to flixos90
  • Status changed from new to assigned

This ticket was mentioned in Slack in #hosting-community by mike. View the logs.

2 weeks ago

Note: See TracTickets for help on using tickets.