Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • I see this, as well, and it breaks the feed. I am able to uncheck the “Add image to RSS/RSS2 feeds” setting in order to make the feed valid again, but I assume we lose images in the feed as a result.

    I’m guessing a this is a bug in the latest version of the Open Graph and Twitter Card plug-in.

    Thread Starter djdavies75

    (@djdavies75)

    Thanks. All the plug-in files are there (including a w3-total-cache/vendor/aws/aws-sdk-php/src/Credentials directory with a Credentials.php file), and the permissions are the same as for everything else in WordPress (plus, they’re world-readable). It certainly seems like the problem is that the CdnEngine_CloudFront.php part of W3TC cannot find the Credentials piece of the AWS SDK, but I don’t know how to fix that.

    As far as I can tell, I have no plug-ins that are doing anything related to AWS, at least not actively. I use one plug-in (Post SMTP) that is capable of using AWS SES, but I’m not using that feature, and W3TC didn’t work any better when Post SMTP was disabled.

    Thread Starter djdavies75

    (@djdavies75)

    @vmarko do you have any more suggestions now that I shared specific errors?

    Thread Starter djdavies75

    (@djdavies75)

    Any additional advice for this? I do not believe I have any other plug-ins that actively use anything AWS-related, so this error surprises me.

    Thread Starter djdavies75

    (@djdavies75)

    This is still a problem for me. I was able to connect to the same S3/CloudFront configuration with the same credentials on a different WordPress installation, so something is unique to the one where I’m having problems. I looked at my webserver logs, and I see:

    2023/12/14 14:40:37 [error] 3437#3437: *17811465 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Error: Class "Aws\Credentials\C                                                                         redentials" not found in /efs/wordpress/wp-content/plugins/w3-total-cache/CdnEngine_CloudFront.php:36
    Stack trace:
    #0 /efs/wordpress/wp-content/plugins/w3-total-cache/CdnEngine_CloudFront.php(179): W3TC\CdnEngine_CloudFront->_init()
    #1 /efs/wordpress/wp-content/plugins/w3-total-cache/Cdn_AdminActions.php(428): W3TC\CdnEngine_CloudFront->test()
    #2 /efs/wordpress/wp-content/plugins/w3-total-cache/Root_AdminActions.php(25): W3TC\Cdn_AdminActions->w3tc_cdn_test()
    #3 /efs/wordpress/wp-content/plugins/w3-total-cache/Generic_Plugin_Admin.php(135): W3TC\Root_AdminActions->execute()
    #4 /efs/wordpress/wp-includes/class-wp-hook.php(324): W3TC\Generic_Plugin_Admin->load()
    #5 /efs/wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #6 /efs/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action()
    #7 /efs/wordpress/wp-admin/admin.php(237): do_action()
    #8 {main}
      thrown in /efs/wordpress/wp-content/plugins/w3-total-cache" while reading response header from upstream, client: 172.30.1.186, server: XXXXX.com, request: "POST /blog/wp-admin/admin.php?page=w3tc_dashboard HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "XXXXX.com",                                                                          referrer: "https://XXXXX.com/blog/wp-admin/admin.php?page=w3tc_cdn"

    It seems like the plugin (or PHP) can’t make some AWS calls, and that would be problematic. Any idea how to resolve this? I’ve tried removing and re-installing the W3TC plugin, but I could try that again.

    Thread Starter djdavies75

    (@djdavies75)

    The problem started after updating W3TC and a few other plug-ins (which I believe I have since tried to disable). I was running WordPress 6.1.3 at that time.

    After that I upgraded to WordPress 6.3 and I updated my theme. to make sure that nothing out-of-date was causing an issue.

    Thread Starter djdavies75

    (@djdavies75)

    The issue is related to some sort of update (I updated several gems, although disabling those does not make this issue go away), but I agree it is not restricted to the W3TC update.

    I have tried different AWS credentials, and they all fail.

    Is there some way to get details beyond “Test Failed” when W3TC tries to initiate an AWS connection?

    My bucket settings and the IAM permissions of the AWS user have not changed, but I will test whether W3TC can work with a different bucket. I don’t expect that to be a part of any solution since I don’t want to move my data to a new bucket.

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