Don't reopen image files that are hosted externally #1605
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1397
This caused crashes on the chooser upload and image edit views.
Some image hosting backends don't allow files to be reopened once closed and will crash with
ValueError("The file cannot be reopened.")
if you tried it.I've seen this issue in the following third-party storage backends:
offsite_storage.storages.S3MediaStorage
storages.backends.s3.S3Storage
storages.backends.apache_libcloud.LibCloudStorage
This PR modifies the
Image.get_willow_image
method to make it get a freshFile
instance if it detects that it is reopening a file that is externally hosted. It also adds some utils to allow us to test against a dummy external storage backend.