Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #33947
    Alex Zupancich
    Guest

    Hi guys,

    I have been using BoldGrid total upkeep and total upkeep premium and its great.
    However it seems to be causing conflicts because of an outdated guzzle library that conflicts with other plugins.
    (Guessing because of your Amazon S3 integration in the premium plugin)

    A plugin I need to uses Guzzle 7.

    I dropped back to an OLD version of this other plugin uses that uses Guzzle 6.3.3. but this still caused a WordPress plugin crash whenever I had Total Upkeep premium enabled.

    Error Details
    =============
    An error of type E_ERROR was caused in line 73 of the file /home/u802513104/domains/learn.jdmis.edu.sg/public_html/wp-content/plugins/boldgrid-backup-premium/vendor/aws/aws-sdk-php/src/Aws/Common/Client/AbstractClient.php. Error message: Uncaught TypeError: Argument 1 passed to Aws\Common\Client\AbstractClient::__construct() must be an instance of Aws\Common\Credentials\CredentialsInterface, array given, called in /home/u802513104/domains/learn.jdmis.edu.sg/public_html/wp-content/plugins/S3MediaVaultPro/vendor/aws/aws-sdk-php/src/MultiRegionClient.php on line 53 and defined in /home/u802513104/domains/learn.jdmis.edu.sg/public_html/wp-content/plugins/boldgrid-backup-premium/vendor/aws/aws-sdk-php/src/Aws/Common/Client/AbstractClient.php:73

    The developer of the other plugin says its not something he can fix – and that its due to a possibly very outdated guzzle version in the Total Upkeep Premium plugin.

    Do you have any suggestions please?

    Thank you!

    Alex

    #33960
    Jesse Owens
    Keymaster

    Hi Alex-

    Thanks for reaching out, I’m sorry to hear about the conflict between S3 Media Vault and Total Upkeep Premium.

    I’ve reached out to the developer at S3 Media Vault to see if they can provide us with a copy of the plugin so we can troubleshoot the error.

    In the meantime, can you let us know a couple more details? Does the error occur as soon as Total Upkeep Premium is activated, or does it only happen on certain pages or during certain tasks, or are there any other steps to replicate the error?

    #33991
    Alex Zupancich
    Guest

    Hi Jesse,
    Thanks for your reply.
    The error happens as soon as I enable both S3 MediaVault and Total Upkeep Premium.
    It does not cause the front-end to fail – the site keeps operating – When I enable Totaul Upkeep Premium causes the S3 Mediavault plugin to fail – visiting the plugin configuration pages triggers a wordpress error email with the error message I submitted.
    Thank you
    Alex

    #33999
    Jesse Owens
    Keymaster

    Hi Alex,

    Thanks a lot for the additional details! Our development team is working on getting a fix for this issue for you. I’ll update you here when we have a release candidate ready. You can also follow the progress on the GitHub issue.

    • This reply was modified 1 year, 9 months ago by Jesse Owens. Reason: Add github issue link
    #34081
    Alex
    Guest

    Hi Jesse,

    The S3MV developer is asking what version of Guzzle you are using?

    Thanks.
    Alex

    #34085
    Ravi Jayagopal
    Guest

    Hi Jesse,

    We had responded to your email the same day we received it, but haven’t heard back. Maybe you didn’t get our email. Have resent it, and here’s what we had originally written:

    Which version of Guzzle are you using in your plugin?

    Version number of Guzzle can be found in: vendor\guzzlehttp\guzzle\src\ClientInterface.php

    You could also let your customer know to download our S3MediaVault v31.3 NO-CONFLICT special version from our website as it incorporates an older version of the Guzzle library (v6.3.3) which is probably causing the conflict they’re facing with your plugin.

    #34165
    Jesse Owens
    Keymaster

    Hello Ravi-

    Thanks a lot for the help! It looks like Alex has already tried the No-Conflict version, and ours is still out-of-date, so our developers are working to update the library now.

    We’ll update the thread here as soon as we have the release ready for testing.

    #34194
    Brad Markle
    Keymaster

    Hi Ravi Jayagopal,

    I’m one of the developers of Total Upkeep.

    In vendor\guzzlehttp\guzzle\src\ClientInterface.php we have:

    /**
     * Client interface for sending HTTP requests
     */
    interface ClientInterface extends HasEmitterInterface
    {
        const VERSION = '5.3.1';

    It looks like both plugins are including the aws-sdk-php library:

    • plugins/S3MediaVaultPro/vendor/aws/aws-sdk-php/
    • plugins/boldgrid-backup-premium/vendor/aws/aws-sdk-php/

    We are running aws/aws-sdk-php version 2.8.31. Which version are you running?

    I also mentioned you in the GitHub issue. Thanks for your help!

    #34241
    Ravi Jayagopal
    Guest

    Hi Brad,

    We’re using AWS PHP SDK v3.x and Guzzle 7.x. We also have a version with Guzzle 6.x in it.

    But it looks like you’re using very old versions of both Guzzle and the AWS PHP SDK.

    Both Guzzle 6 and AWS PHP SDK 3.x were released in 2015. So you are using 6 year old versions of both SDK’s. So you would need to update your plugin to more recent versions.

    Just updating to a newer version of AWS SDK will take care of Guzzle too.

    #34272
    Jesse Owens
    Keymaster

    Hi Ravi-

    Thanks for the feedback! Brad and the team are working on the updates now, and we expect to have a release within a week or so, depending on any hurdles we hit with the updated library.

    #34603
    Brad Markle
    Keymaster

    Hi Alex,

    This week I was able to upgrade our version of the aws-sdk-php library from version 2 to 3. There was some development work required. I did run into some snags – unfortunately I wasn’t able to get a release out this week like I wanted.

    I think we’re ready to release the updates for Total Upkeep Premium though, we’re in the final testing phase now. It’s generally not a good idea to release on Friday’s, but hopefully early next week we’ll be able to release the updates.

    Thanks for your patience Alex – we’ll keep you updated.
    – Brad

    #34952
    Brad Markle
    Keymaster

    Hi Alex,

    We’ve been working a bit throughout the week on this update. We’ve got the Amazon PHP SDK updated to version 3, and we also updated a few other things as well.

    These features have been released in Total Upkeep Premium 1.5.8.

    Are you able to update your version and test? You can’t actually click “Update” within WordPress to get this new version. Please instead click the link above to download the zip file, and then upload that to WordPress.

    Thanks for all patience through all this, and we’re waiting to hear how everything goes!
    – Brad

    #34960
    Alex Zupancich
    Guest

    Thank you BoldGrid Team and Ravi from S3MV.

    Your new update works just fine with S3MVs newer version of guzzle.
    Appreciate everyone’s help making updates and collaborating on a fix!

    Have a good weekend.
    Alex

Viewing 13 posts - 1 through 13 (of 13 total)
  • The topic ‘Total Upkeep Premium Amazon S3 Conflict: Argument 1 passed to Aws/Common/Client/AbstractClient::__construct() must be an instance of Aws/Common/Credentials/CredentialsInterface, array given’ is closed to new replies.