dev

It would be nice to have this feature however only when switching currencies not on the initial load.

our prices are there already so there is no need to pre-load the base currency in. It would just help make the slow switching of currencies appear better.

We would rather not put our site URLS on a public forum. Is there a way to send these privately?

Hello,

Do you have an email address I can send it to ?

Correct however it applies this to the base currency and this increases the time until the prices are displayed. It should only be used when switching currencies not on initial load.

Hello,

The page load speed is not the issue, it is the time it takes to switch currencies after the page has loaded. This is very slow and takes several seconds to switch currencies.

In regards to our site, when the pre-loader is enabled it pre-loads the base currency which is not needed.

Kind Regards

• This reply was modified 3 years, 7 months ago by dev.

We have the same error

I’ve raised a ticket on your portal, thank you.

Hello,

Thank you for the quick response.

Do you have an email address I can send these to ?

Kind Regards

So when using the workaround to exclude the w3tc awslibs via wp-config, it results in a “‘Aws\\S3\\S3Client’ not found ” error and the cloudfront CDN breaks as a result.

No that’s a separate issue entirely. We have a temp-patched version of activity logger which excludes the AWS libs and now does not conflict with w3tc. Our issue was raised with the devs directly not via the WP forum.

It’s definitely being caused by an AWS library conflict.

This is correct.

They are also aware of this as well but we’ve had to disable one plugin to have the other work currently.

Hello,

Unfortunately this does not resolve the issue. I then get the following error:

[Fri Jun 18 17:54:18.421544 2021] [proxy_fcgi:error] [pid 11425:tid 140027677865728] [client 172.69.54.15:44174] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught Error: Class 'Aws\\S3\\S3Client' not found in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/CdnEngine_S3.php:107\nStack trace:\n#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/CdnEngine_S3.php(369): W3TC\\CdnEngine_S3->_init()\n#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/CdnEngine_CloudFront.php(171): W3TC\\CdnEngine_S3->test()\n#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/Cdn_AdminActions.php(428): W3TC\\CdnEngine_CloudFront->test()\n#3 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/Root_AdminActions.php(25): W3TC\\Cdn_AdminActions->w3tc_cdn_test()\n#4 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/Generic_Plugin_Admin.php(165): W3TC\\Root_AdminActions->execute()\n#5 /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-hook.php(292): W3TC\\Generic_Plugin_Admin->load()\n#6 /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-hook.ph...', referer: https://SITE.uk/wp-admin/network/admin.php?page=w3tc_cdn
[Fri Jun 18 17:54:57.605547 2021] [proxy_fcgi:error] [pid 7238:tid 140026503378688] [client 172.69.54.15:46560] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught Error: Class 'Aws\\S3\\S3Client' not found in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/CdnEngine_S3.php:107\nStack trace:\n#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/CdnEngine_S3.php(369): W3TC\\CdnEngine_S3->_init()\n#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/CdnEngine_CloudFront.php(171): W3TC\\CdnEngine_S3->test()\n#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/Cdn_AdminActions.php(428): W3TC\\CdnEngine_CloudFront->test()\n#3 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/Root_AdminActions.php(25): W3TC\\Cdn_AdminActions->w3tc_cdn_test()\n#4 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/w3-total-cache/Generic_Plugin_Admin.php(165): W3TC\\Root_AdminActions->execute()\n#5 /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-hook.php(292): W3TC\\Generic_Plugin_Admin->load()\n#6 /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-hook.ph...', referer: https://SITE.uk/wp-admin/network/admin.php?page=w3tc_cdn

This looks like its being caused by a conflict with WP-Activity logger … Disabling the plugin resolves the issue.

I’ve raised this with their dev team.

So we’ve setup the CDN + S3 to default however still getting the same error when trying to test access.

Not sure if there is some issue with the Total cache config ?

So this is with a multisite setup and they’re all using the same config.

Yes thats correct

So we cannot authorize it at all as that error is produced when trying to “Test S3 upload & Cloudfront distribution”.

We’ve even tried new keys but it seems that the AWS config isn’t being accepted by the AWS SDK.

We’re using version 7.4.16 currently

The “Not a valid retry configuration” seems to be generated fromthe AWS SDK code “ConfigurationProvider.php”

* Unwraps a configuration object in whatever valid form it is in,
* always returning a ConfigurationInterface object.
*
* @param mixed $config
* @return ConfigurationInterface
* @throws \InvalidArgumentException
*/
public static function unwrap($config)
{
if (is_callable($config)) {
$config = $config();
}
if ($config instanceof PromiseInterface) {
$config = $config->wait();
}
if ($config instanceof ConfigurationInterface) {
return $config;
}

// An integer value for this config indicates the legacy ‘retries’
// config option, which is incremented to translate to max attempts
if (is_int($config)) {
return new Configuration(‘legacy’, $config + 1);
}

if (is_array($config) && isset($config[‘mode’])) {
$maxAttempts = isset($config[‘max_attempts’])
? $config[‘max_attempts’]
: self::DEFAULT_MAX_ATTEMPTS;
return new Configuration($config[‘mode’], $maxAttempts);
}

throw new \InvalidArgumentException(‘Not a valid retry configuration’
. ‘ argument.’);
}

It looks like it started 19 days ago and the S3 CDN no longer works.