Skip to content
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

Broken on django-storages >= 1.14.4 #1484

Open
petrklus opened this issue Jul 30, 2024 · 2 comments
Open

Broken on django-storages >= 1.14.4 #1484

petrklus opened this issue Jul 30, 2024 · 2 comments
Labels

Comments

@petrklus
Copy link

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: jschneier/django-storages#1430

@fsbraun
Copy link
Member

fsbraun commented Jul 31, 2024

@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.

Copy link

stale bot commented Oct 29, 2024

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.

@stale stale bot added the stale label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants