Monitor Reply

Support

Upload Failed die to incorrect API version

Permalink Browser Info Environment July 01, 2016 at 2:28 PM

My ability to upload to S3 has terminated due the API version being set as latest. I get the following message in an "upload failed" box

FB_IMG_1462877581077.jpg
Missing required client configuration options: version: (string) A "version" configuration value is required. Specifying a version constraint ensures that your code will not be affected by a breaking change made to the service. For example, when using Amazon S3, you can lock your API version to "2006-03-01". Your build of the SDK has the following version(s) of "s3": * "2006-03-01" You may provide "latest" to the "version" configuration value to utilize the most recent available API version that your client's API provider can find. Note: Using 'latest' in a production application is not recommended. A list of available API versions can be found on each client's API documentation page:http://docs.aws.amazon.com/aws-sdk-php/v3/api/index.html.... If you are unable to load a specific API version, then you may need to update your copy of the SDK.

Unfortunately I can't see where this can updated in the code. Can you help please?

Type:	Ticket
Status:	Archived

gordoncWG replied on Jul 1, 2016 at 5:16 pm Permalink Reply

I have been able to ascertain that this issue is being caused by the installation of another package I have created and installed that uses the AWS PHP SDK.

However, I can't work out how to resolve the conflict.

The Amazon S3 package doesn't seem to specify a version to be used anywhere in it's code. Would this resolve the problem?

gordoncWG replied on Jul 2, 2016 at 5:43 am Permalink Reply

I'm afraid I can't work out how to resolve this. Both the package I have created which sets cookies to access private content via AWS Cloudfront and the Storage for Amazon S3 package work fine on their own. However, when my package is installed it causes Storage for Amazon S3 to throw the "version required" error message.

I'm assuming C5 must be encountering some sort of conflict with the SDK in two different packages but I can't work out how to resolve it.

If I was to provide my package zipped could you help please?

Mnkras replied on Jul 2, 2016 at 4:53 pm Permalink Reply

Does your addon use v2 or v3 of Amazon's SDK?

I think that error only happens in v3 and this addon uses v2.

Mike

gordoncWG replied on Jul 3, 2016 at 10:30 am Permalink Reply

My package uses v3. I don't know if it will work with v2 but could try.

Is there no way C5 can handle one being used for one package and another being used for the other though?

gordoncWG replied on Jul 3, 2016 at 2:05 pm Permalink Reply

I've tried to make the package work with v2 of the SDK but I'm getting errors. I'm setting cookies and the code I'm using is for v3 of the SDK. And I can't see code examples for v2.

I'm kind of stuck.

Mnkras replied on Jul 3, 2016 at 9:09 pm Permalink Reply

Can you send the package over to me? <myusername>@gmail.com

Ill try and take a look, I have a newer version of the package running v3 but its made for c5v8.

The primary issue is that the autoloader is trying to load 2 different versions of the SDK and they don't have different namespaces.

Mike

ConcreteCMS replied on Jul 18, 2016 at 12:05 am Permalink Reply

Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.

To re-open this issue, reply to this message.

Storage for Amazon S3

Support

Upload Failed die to incorrect API version

Issue Reply

concrete5 Environment Information

Browser User-Agent String

Hide Post Content

Request Refund

Code

Delete Post