Fix problem where polymorphic_disabled not always present. - #1
Open
stuaxo wants to merge 1 commit into
Open
Conversation
Owner
|
The latest should fix this issue and also make |
Author
|
Verified and it doesn't work everywhere yet (see comment on patch). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi,
Not sure if this is technically the right fix, but a query using __in was complaining about the field polymorphic_disabled not being on the model (query.py, line 37). I've worked around this using getattr for the moment.
Cheers,
Stuart