409 Already Exists results in unsynchronized image

cloudinary / cloudinary_magento

Cloudinary's Magento extension. Upload product images to the cloud, manipulate them to match your graphic design and optimize images for better user experience

MIT License

16 stars 17 forks source link

409 Already Exists results in unsynchronized image #11

Closed andyt closed 7 years ago

andyt commented 8 years ago

If an image already exists in Cloudinary, the returned 409 AlreadyExists error should be caught and the image tagged as synchronized.

taragano commented 8 years ago

Hi @andyt,

Can you please share some more information regarding the flow and use-case? Did you re-upload an image, trying to update (overwrite) an existing one? Was this error returned during a single image upload or the bulk migration?

andyt commented 8 years ago

This is during migration of images to Cloudinary using the Magento plugin. My database was reimported without the cloudinary migration table data, so I restarted the migration. Images which were re-uploaded but existed on Cloudinary already were blocking the migration, as they were recorded as errors, whereas in fact they simply need to be tagged as synchronized.

I've forked the plugin and fixed the problem (and am now fully synchronized). However, I am struggling to run the tests due to composer dependency issues.

grantkemp commented 8 years ago

@andyt can you share your code?

andyt commented 8 years ago

https://github.com/cloudinary/cloudinary_magento/pull/12

idobarnoam commented 7 years ago

Hi @andyt I'm closing this thread since you are no longer having this issue. And there is an outstanding pull request. Please feel free to either re-open the issue, contact our support http://support.cloudinary.com or create a new ticket if you have any additional issues.