PHP Fatal Error – Conflict with WPDM Amazon S3 Plugin

  • Resolved midihead

    (@midihead)


    2 years, 9 months ago

    Like others, I’m getting a PHP fatal error when UpdraftPlus 1.22.5 tries to connect to Amazon S3. This started recently with an recent UpdraftPlus update. The error I get is in relation to the WPDM Amazon S3 plugin (version 3.0.3) from Download Manager.

    PHP Fatal error (Error) has occurred during test_storage_settings subaction. Error Message: Call to undefined method GuzzleHttp\Utils::chooseHandler() (Code: 0, line 61 in .../wp-content/plugins/wpdm-amazon-s3/aws-sdk/vendor/guzzlehttp/guzzle/src/functions.php)

    Download Manager support is trying to say that UpdraftPlus is using an old S3 API (which I doubt):

    "It seems updraft is using old AWS API, which is creating such conflict. In that case, it needs to be fixed from their side."

    Putting define('UPDRAFTPLUS_S3_OLDLIB', true); in my wp-config.php file allows UpDraftPlus to connect to S3 again. This working seems to indicate that UpdraftPlus is using a newer library in the latest release.

    If this really is an issue with the WPDM Amazon S3 plugin using an old S3 library, what is the official answer I can give to Download Manager support as the real source of the problem?

    Thank you very much.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author David Anderson

    (@davidanderson)

    > “It seems updraft is using old AWS API, which is creating such conflict. In that case, it needs to be fixed from their side.”

    This is indeed wrong – we are using AWS SDK PHP version 3.209.30, released only 3 days ago: https://github.com/aws/aws-sdk-php/releases/tag/3.209.30 . This can be verified by looking in the Composer digest of used version in UpdraftPlus: https://plugins.svn.www.ads-software.com/updraftplus/tags/1.22.5/vendor/composer/installed.php

    The actual problem is that WPDM Amazon S3 is loading its libraries on every single WordPress request (front-end, back-end, JSON, AJAX). In particular, it loads them on UpdraftPlus’s pages and requests. Because of the conflict, an error occurs. If UpdraftPlus loaded its versions on every request like this, it would be your entire site that was down, every page, not just UpdraftPlus contexts. They should only load their libraries when about to contact Amazon S3, not on every request, and certainly not on other plugins’ settings pages and requests. Your site only continues to load because there aren’t other plugins doing the same – as soon as you get one that does, it’ll go down everywhere.

    Using the define mentioned above is a work-around you can use whilst that persists.

    David

    Thread Starter midihead

    (@midihead)

    Thank you David for that detailed explanation. I have passed this information on to WPDM Amazon S3 support in hopes that this will get corrected quickly.

    Thread Starter midihead

    (@midihead)

    WPDM Amazon S3 support has released an update that fixes the conflict with UpdraftPlus. Many thanks for your help.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘PHP Fatal Error – Conflict with WPDM Amazon S3 Plugin’ is closed to new replies.