[REVIEW] 466 - Fix created object owner definition #484
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.
Description
I found the bug that was generating the TypeError described in issue #466.
Apparently someone was confusing the
owner
andauthor
fields and was using theprofile
object for the form, since the form only supports theauthor
textual field.The solution, according to the Django documentation, is to first create the object and then associate the created object with the logged in user.
Resolves (Issues)
#466 - Create a object results in a TypeError
General tasks performed
upload_elements
functionHave you confirmed the application builds locally without error? See here.