Bug caused by updated to how Flask handles the file upload field #5020
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.
… filename for the file_url field when I'm not actually uploading a new file, just changing other metadata (such as description). This effectively kills kills the uploaded image link for the organization/groups.
Fixes #
Proposed fixes:
Issue occurs only when I have an image for the organization/groups. I need to be able to update other metadata but not uploading a new image. It breaks due to the fact how old Pylons requests object not returning anything in the "image_upload" field when the user doesn't upload a new image. Flask's FileStorage class has a boolean check instead where we can just do if "data_dict['image_upload']" or similar instead.
I have kept the original if statement in place to be backwards compatible, additional check added in order to account for the Flask method.
Features:
Please [X] all the boxes above that apply