Open petrklus opened 4 months ago
@petrklus Thanks so much for bringing this to attention! For now, django-filer needs to work with django-storages<=1.14.3.
Django has clarified the ways .exists()
works in their development branch (https://docs.djangoproject.com/en/dev/ref/files/storage/#django.core.files.storage.Storage.exists) and my understanding is that django-storages will revert to this updated definition in its next minor release.
I suggest to wait for the changes in the next django-storages release and see from there, if filer needs an update.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@fsbraun has there been any update on this? Still behaves the same, do the django-storages team have any ETA for the release?
Due to the change with how .exists() works when used with certain backends, Django-filer is now broken as it relies on .exists to return actual file existence (and not False). This happens for me on S3 backed storage (not locally).
Further detail: https://github.com/jschneier/django-storages/issues/1430