Conflict with W3 Cache CDN

  • rogerpz81

    (@rogerpz81)


    3 years ago

    Hi!

    One of the last updates is causing a conflict with the W3 Cache authentication with AWS.

    I am getting this error:

    Error Details
=============
An error of type E_ERROR was caused in line 158 of the file /var/www/viva/myvegantown.org.uk/htdocs/wp-content/plugins/w3-total-cache/vendor/aws/aws-sdk-php/src/Credentials/CredentialProvider.php. Error message: Uncaught Error: Call to undefined function GuzzleHttp\Promise\promise_for() in /var/www/viva/myvegantown.org.uk/htdocs/wp-content/plugins/w3-total-cache/vendor/aws/aws-sdk-php/src/Credentials/CredentialProvider.php:158
Stack trace:
#0 /var/www/viva/myvegantown.org.uk/htdocs/wp-content/plugins/w3-total-cache/vendor/aws/aws-sdk-php/src/ClientResolver.php(443): Aws\Credentials\CredentialProvider::fromCredentials()
#1 /var/www/viva/myvegantown.org.uk/htdocs/wp-content/plugins/w3-total-cache/vendor/aws/aws-sdk-php/src/ClientResolver.php(323): Aws\ClientResolver::_apply_credentials()
#2 /var/www/viva/myvegantown.org.uk/htdocs/wp-content/plugins/w3-total-cache/vendor/aws/aws-sdk-php/src/AwsClient.php(199): Aws\ClientResolver->resolve()
#3 /var/www/viva/myvegantown.org.uk/htdocs/wp-content/plugins/w3-total-cache/CdnEngine_Mirror_CloudFront.php(43): Aws\AwsClient->__construct()
#4 /var/www/viva/myvegantown.org.uk/htdocs/wp-content/plugins/w3-total-cache/CdnEngine_Mirror_CloudFront.php(203): W3TC\CdnEngine_Mirror_Cloud

    Is there something we can do to fix this problem?

    Thank you very much for your support!

Viewing 2 replies - 1 through 2 (of 2 total)

  • @rogerpz81 so I can’t replicate this. Out of interest if you disable my plugin do you still get this error. Given I’ve now namespaced the libraries my plugin uses, I would expect the cache plugin to still be failing without my plugin enabled. If it still fails, the reason is because the cache plugin is requiring GuzzleHTTP, but isn’t loading it.

    My plugin was previously loading the GuzzleHTTP library without namespacing, so the cache plugin could have been piggybacking on that, but now I’ve namespaced it (to avoid conflicts with plugins that are loading libraries without namespacing them), you’re getting an error, as it can’t find GuzzleHTTP.

    This is my hunch, based on the error, and the fact the only change is that I’ve now namespaced the libraries (ironically to avoid conficts…)

    Thread Starter rogerpz81

    (@rogerpz81)

    Thanks for your replay Edward,

    If I disable your plugin, the CDN service works again.

    I am using your plugin version 1.7.1 and the CDN service and the mailing works now.

    The CDN plugin we are using is W3 with Amazon Cloud Front. This is a very popular plugins so I wonder if there is something else we can do.

    Warm regards,

    Roger

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with W3 Cache CDN’ is closed to new replies.

Tags