Open jomopeh opened 6 years ago
This is very strange.
Did you make anything strange with the source (not normal model form) or something?
Did you changed IMAGEKIT_SPEC_CACHEFILE_NAMER
and/or IMAGEKIT_CACHEFILE_NAMER
?
Hi vstoykov,
I have not modified those settings. I could not find what the problem was. What I can say is that I use django storages (S3) alongside. Whether it's an incompatibility, or s3 storage settings causing the issue, I cannot say.
I suspect it was caused some duplicate name conflict or perhaps ImageSpecField lost reference to the file. After lots of debugging, it looks like it was using the first image that was ever saved, weird.
Either way, unfortunately I have moved away from image-kit for this use case as I had limited time to continue debugging.
After upgrading the relevant packages and reconfiguring django storages, all is well now alongside S3.
Thank you
I'm using ImageSpecField on a model like so:
I noticed that one of the image instance I have saved, contains a different image for the image_thumbnail and image_medium, than the image field.
But all other times (99%) uploads remain consistent and the image_thumbnail and image_medium reflect the source image field.
Could this be a problem with the image name that is being passed when the image is uploaded, causing name conflict? Or a bug with ImageSpecField? I'm currently on django-imagekit==4.0.1
Thanks