When WP_DEBUG is true show better errors for establishing database connection

[sivel]

Right now no matter if WP_DEBUG is enabled or not we always show some generic errors for Error establishing a database connection

We should display the specific error when WP_DEBUG is enabled.

[sivel]

Patch is just an idea of how we might do this. Open to other suggestions and patches.

[nacin]

I would tend to think we should not be exposing the output of mysql_error() on any site. Or, if we do, then we at least also check for display_errors/WP_DEBUG_DISPLAY, in case they want WP_DEBUG (as can be common in production) but are logging it.

[sivel]

The way that translations are handled for these errors makes it difficult to do conditionals like this. Mainly due to duplicating large portions of code and strings. Well maybe not large but more than I am comfortable with duplicating.

I may just need to stare at the code for a bit to get a creative solution, that is unless someone has recommendations.

[pento]

The strings have since been split up, making it much easier to insert a conditional string when WP_DEBUG and WP_DEBUG_DISPLAY are defined.

[Mte90]

check for WB_DEBUG and WP_DEBUG_DISPLAY

[Mte90]

I updated the patch but I am not sure about mysql_error because maybe wpdb have a wrapper for that but I am not an expert for this part.

[pento]

It would be best to put this in wpdb::bail(). That method will always be the one called when WPDB needs to kill page loading. There's no need to check WP_DEBUG && WP_DEBUG_DISPLAY here, as wpdb::$show_errors is set to that.

I would suggest appending it to $message at the start. Also, don't forget to check mysqli_error(). :-)

[Mte90]

new patch with in bail method

[SergeyBiryukov]

In 42716:

Database: If both WP_DEBUG and WP_DEBUG_DISPLAY are true, display a more specific error message in wpdb::bail().

Props sivel, Mte90, SergeyBiryukov.
Fixes #13657.

Building on @swissspidy's wp_safe_remote_request_multiple() in PR #13657, I have implemented download_url_multiple() and wired it into Plugin_Upgrader::bulk_upgrade() and Theme_Upgrader::bulk_upgrade().

Benchmark Results (5 Real WP.org Packages)

Tested downloading 5 real production plugins (hello-dolly, wp-multibyte-patch, classic-widgets, regenerate-thumbnails, duplicate-post):

• Sequential (download_url): 6.315s
• Concurrent (download_url_multiple): 2.147s
• Speedup: 2.94x faster (66% latency reduction)

Implementation Summary

1. download_url_multiple() added to src/wp-admin/includes/file.php with concurrent streaming.
2. Extracted private _wp_handle_download_response() helper, removing code duplication between single and multiple downloads (shares Content-Disposition, MIME checks, MD5 verification, and .sig checks).
3. Plugin_Upgrader & Theme_Upgrader pre-fetch compatible packages in parallel before the update loop; unconsumed files are cleaned up safely.
4. Resilience: Automatic fallback to package URL if any single batch item fails.
5. Full Tests: Added dedicated unit tests in downloadUrlMultiple.php (7 tests, 33 assertions) and integration tests in bulkUpgrader.php (3 tests, 14 assertions). 100% passing; 0 PHPCS warnings/errors.

Branch: feature/bulk-upgrader-concurrent-downloads
Full details and implementation notes: See attached PR description.

Building on @swissspidy's wp_safe_remote_request_multiple() in PR #13657, I have implemented download_url_multiple() and wired it into Plugin_Upgrader::bulk_upgrade() and Theme_Upgrader::bulk_upgrade().

Benchmark Results (5 Real WP.org Packages)

Tested downloading 5 real production plugins (hello-dolly, wp-multibyte-patch, classic-widgets, regenerate-thumbnails, duplicate-post):

• Sequential (download_url): 6.315s
• Concurrent (download_url_multiple): 2.147s
• Speedup: 2.94x faster (66% latency reduction)

Implementation Summary

1. download_url_multiple() added to src/wp-admin/includes/file.php with concurrent streaming.
2. Extracted private _wp_handle_download_response() helper, removing code duplication between single and multiple downloads (shares Content-Disposition, MIME checks, MD5 verification, and .sig checks).
3. Plugin_Upgrader & Theme_Upgrader pre-fetch compatible packages in parallel before the update loop; unconsumed files are cleaned up safely.
4. Resilience: Automatic fallback to package URL if any single batch item fails.
5. Full Tests: Added dedicated unit tests in downloadUrlMultiple.php (7 tests, 33 assertions) and integration tests in bulkUpgrader.php (3 tests, 14 assertions). 100% passing; 0 PHPCS warnings/errors.

Branch: feature/bulk-upgrader-concurrent-downloads
Full details and implementation notes: See attached PR description.