-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during unserialisation #12
Comments
Hey @jiitpiyush, Thanks. It looks to be a problem with the new metadata feature I added the other day. :/ I'll get back to you soon. Regards, Thai |
Hey @jiitpiyush, I've just pushed up a new version that should address your problem. Can you install and review? Regards, Thai |
Hi @thaiphan , |
That's a pretty vague problem, sorry. Were you successfully uploading previously or did it stop working with the latest change? Did you properly setup your S3 configuration? |
I take first pull from your repo yesterday and I'm getting issues. S3 is configured properly. |
So you installed the extension for the first time yesterday? I just tested your scenario with the latest version and it's working. Are you sure that you have your S3 bucket / region set up properly? Sometimes people are in the wrong region. |
I checked and found that My region is ap-south-1 and this region doesn't exists in your List. Can you please add this? |
Hi @thaiphan, I checked your code and added ap-south-1 region to helper , but still issue persist as media is not uploading to S3. Can you please guide me where to debug? |
Hi @jiitpiyush, I think this is a continuation of #4. I'm using Magento's built-in S3 client, which is super old and doesn't support the new V4 Signature Signing. It only supports V2 for the time being. The Regards, |
Hey @jiitpiyush, I'm closing this issue because I'm tracking it in #4 already. I hope that's okay. Regards, Thai |
When uploading images to a product, I'm getting an error during serialization.
This issue exists after the new pull on May 26, 2018 (last commit id a154467).
The text was updated successfully, but these errors were encountered: