You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the image that "thumbnail_url" points to is not the same as "thumbnail_url"?????
My question is, without going through all the details, is there a possibility that sorl thumbnail via the get_thumbnailer method will render/use a different image than the source image, even though I reference that image field?
I understand sorl-thumbnail uses the key value architecture as a cache store, which I assume is unique and there will not be any name conflicts.
(I actually have a use case, where uploading images works consistently when uploading through either android or desktop browsers, but apparently if it's uploaded through iOS browser then issues such as I described above appears. I'm actually wondering whether this is a problem with django storages s3 instead, or some issue on the client).
Thanks for any feedback
The text was updated successfully, but these errors were encountered:
For each image I upload, I'm using get_thumbnailer on that source image and returning the url, which in my case will link to S3.
on model:
image = ImageField(upload_to='images')
then "image" is passed to get_thumbnail:
get_thumbnail(image, '200', crop='center', quality=99).url
the image that "thumbnail_url" points to is not the same as "thumbnail_url"?????
My question is, without going through all the details, is there a possibility that sorl thumbnail via the get_thumbnailer method will render/use a different image than the source image, even though I reference that image field?
I understand sorl-thumbnail uses the key value architecture as a cache store, which I assume is unique and there will not be any name conflicts.
(I actually have a use case, where uploading images works consistently when uploading through either android or desktop browsers, but apparently if it's uploaded through iOS browser then issues such as I described above appears. I'm actually wondering whether this is a problem with django storages s3 instead, or some issue on the client).
Thanks for any feedback
The text was updated successfully, but these errors were encountered: