Support » Alpha/Beta/RC » Fatal error during update to 5.9 Beta 1

  • Got a fatal error during update from 5.8.2 to 5.9 beta 1 via Beta Tester plugin. Here it is:

    Fatal error: Uncaught Error: Class "Requests_Exception" not found in \wp-includes\Requests\Transport\cURL.php:443
    
    Stack Trace
    1.	
    Requests_Transport_cURL->process_response('', Array)
    \wp-includes\Requests\Transport\cURL.php:179
    2.	
    Requests_Transport_cURL->request('https://test...', Array, NULL, Array)
    \wp-includes\class-requests.php:381
    3.	
    Requests::request('https://test...', Array, NULL, 'POST', Array)
    \wp-includes\class-http.php:394
    4.	
    WP_Http->request('https://test...', Array)
    \wp-includes\class-http.php:608
    5.	
    WP_Http->post('https://test...', Array)
    \wp-includes\http.php:179
    6.	
    wp_remote_post('https://test...', Array)
    \wp-admin\includes\update-core.php:1409
    7.	
    update_core('C:/Programs/lar...', 'C:/Programs/lar...')
    \wp-admin\includes\class-core-upgrader.php:172
    8.	
    Core_Upgrader->upgrade(Object(stdClass), Array)
    \wp-admin\update-core.php:877
    9.	
    do_core_upgrade(false)
    \wp-admin\update-core.php:1106
    10.	
    {main}
    thrown in \wp-includes\Requests\Transport\cURL.php on line 443

    For the local environment I am using Laragon and Windows 10. And I can see Exception.php in Requests folder.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Marius L. J.

    (@clorith)

    Hiya,

    Thank you for the report, we’re looking into this, in relationship with a similar issue (#54544). We’re not confident yet if it’s the same issue, or a different one with similar effects, so I’m not going to ask you to make a ticket until we’ve been able to dig a little bit more into this, but we will keep you updated.

    Until then, you may do a manual update, either to WordPress 5.8.2, or to the 5.9-beta1, which will hopefully resolve this for you.

    Thread Starter titsmaker

    (@titsmaker)

    My case seems similar but not identical – I have all the files in place, their content is updated, but the name stayed the same indeed. I have cURL instead of Curl, SSL instead of Ssl, etc.
    After some testing it seems updated WP works fine despite the error during update.
    I was able to update a clean install of WP in the same local environment without issues and I was able to recreate the error for the local copy of my site. So it’s due to some configuration or plugins. Though I should say it was updated without errors many times before.

    Tonya Mork

    (@hellofromtonya)

    Hello @titsmaker,

    Thank you for reporting this problem. It’s been resolved in 5.9 Beta 2 which is available for testing. Please see the announcement post.

    Interested to learn if you experience problems upgrading to Beta 2.

    Thread Starter titsmaker

    (@titsmaker)

    The update went smoothly this time.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.