Ryan McCue

You'll need to check your PHP error log to find out exactly what the error here, as I believe this message is a generic error message when something fails to...

Appreciate the feedback here. We'll aim not to intentionally break compatibility with anyone who wants to manually install the plugin and the SDK, and we won't require installation via Composer...

This has been merged, and the only supported installation method now is via Composer.

We haven't received any similar notices and use TLS 1.2 extensively in production, so I suspect it works fine. I would assume the AWS SDK handles any of this seamlessly...

Thanks for the ping here, we actually _did_ get a ping today, but only for our us-east-1 region and not any others. I'm wondering if it might be related to...

Noting that the affected resource notes a user agent of: ``` Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media...

I think this is best left in the control of those using S3 Uploads rather than within the plugin itself?

This can be filtered with `add_filter( 'pre_site_option_upload_space_check_disabled', '__return_false' )` in your code. The question is whether we add that filter to S3 Uploads by default. I could imagine this functionality...

The media library will be reading your images from S3 rather than the local filesystem so you should expect this to be slower. The pagination in place should take care...

@marsjaninzmarsa I think @kucrut literally means the `[attachment:...]` syntax matching. We do also need to fix those other URLs though; can you file an issue for that? :)