Opened 18 months ago
Closed 18 months ago
#63052 closed defect (bug) (fixed)
Extension check during upgrade does not work on WordPress prior to 5.1
| Reported by: | johnbillion | Owned by: | johnbillion |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.8 |
| Component: | Upgrade/Install | Version: | 6.9 |
| Severity: | major | Keywords: | has-patch |
| Cc: | Focuses: |
Description
As discovered by the upgrade checks for 6.8 beta 1, the check for missing required extensions during the upgrade process that were added in [59803] calls the WP_Error::has_errors() method which was introduced in WordPress 5.1. This means sites running WordPress prior to 5.1 will experience a fatal during the upgrade process.
The site will remain online and functional, but it won't be possible to proceed with the upgrade.
Example failing workflow: https://github.com/WordPress/wordpress-develop/actions/runs/13657290367/job/38180581900
Change History (6)
This ticket was mentioned in Slack in #core by jeffpaul. View the logs.
18 months ago
This ticket was mentioned in PR #8457 on WordPress/wordpress-develop by @johnbillion.
18 months ago
#2
- Keywords has-patch added; needs-patch removed
This ticket was mentioned in Slack in #cli by swissspidy. View the logs.
18 months ago
This ticket was mentioned in Slack in #core by benjamin_zekavica. View the logs.
18 months ago
#5
@
18 months ago
This error causes some WP-CLI tests to fail too, see https://github.com/wp-cli/core-command/actions/runs/13743595251/job/38436006640#step:11:135
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Trac ticket: https://core.trac.wordpress.org/ticket/63052
I've added a develop upgrade check for WordPress 5.0 too, but we might need to exclude this from running on PHP 8.4. Let's see what the tests tell us.