Open Vadorequest opened 5 years ago
Note that this may actually be the right way to do it, I've not tested it yet though: https://docs.djangoproject.com/en/2.1/ref/contrib/contenttypes/#generic-relations-in-admin
+1 I can confirm this issue. Same happening when calling a genericforeignkey object via manage.py shell.
In my case I had two genericforeignkeys in one model, both defined by using individual attribute names (e.g. "x_content_type" instead of "content_type", "x_object_id" instead of "object_id").
Workaround: Define at least one genericforeignkey by using the default attribute names "content_type" and "object_id" and everything works magically.
I am also facing this issue still. For limited things that I have tried - seems like GenericRelation is causing the problem (which is required if I want to filter my based on GenericForeignKey).
Getting the generic fk entity itself is working after filtering even if object_id is not the name. So I think GenericRelation is the problem
Regarding the above comment, sorry if this doesn't belong here. I am using normal django only. Not sure what jet-django is. But seems like the same issue. Redirect to the correct issue if there is one.
I have the following dynamic entity in one of my models:
When I update the entity through the Jet Admin UI such as:
I get the following error on the backend logs:
I do not experience this issue when I use the Django Admin interface.
Solution
Renaming the model fields to the following fixed the issue:
I guess something is hardcoded on the jet-django package and it doesn't handle custom model variable for dynamic relationships. I only have one in my case so it's not blocking, just annoying, but this should be fixed.