Hi issuer, Plz look at model built by UpdateWithInlinesView to see if you mistake from limit of string return from get_absolute_url() https://django-extra-views.readthedocs.io/en/latest/pages/formset-views.html#createwithinlinesview-and-updatewithinlinesview
https://docs.djangoproject.com/en/2.2/ref/models/instances/ must contain ASCII RFC2396 section 2 On Sat, Dec 7, 2019, 20:27 Daniel Chimeno <[email protected]> wrote: > +1 to more document about DEBUG magic. > > > El sábado, 7 de diciembre de 2019, 0:08:41 (UTC+1), Alaina Rowe escribió: >> >> I have not been able to reproduce the bug I am about to describe when >> DEBUG is True, whether in production on Apache or locally on the Django dev >> server. So my first question is: What is all the magic that Django DEBUG >> does behind the scenes? The documentation doesn't have very much >> information about this. >> >> Now for the bug. I understand that the following description is too >> bare-bones for anyone to reproduce, but I have IP to protect, and I don't >> have much hope of the error being reproduced anyway. >> >> Suppose I have a Django project with at least two apps, app alice with >> model A and app bob with model B. >> >> I am using UpdateWithInlinesView from django-extra-views. The error >> occurs when this view constructs a formset from instances of model A. In my >> email about the 500, I get a message like this: >> >> FieldError at /some/url/ >> Cannot resolve keyword 'field_of_A' into field. Choices are: >> field_of_B_1, field_of_B_2, field_of_B_3 >> >> I've gotten this type of error before. It normally happens when you tell >> a form "I'm using model C" and "I'm using a field called debbie" and model >> C doesn't have a field called debbie. That part makes sense. But this error >> makes it look like it's checking against the field names of model B when it >> should be checking model A. I have been racking my brain trying to figure >> out how in the world the construction of a form from one model would >> consult a different model from a different app. >> >> Furthermore, this doesn't happen most of the time, it goes away on server >> restart, and it doesn't happen under DEBUG = True. So I'm wondering if it's >> an app registry issue, some sort of race condition that gets the registry >> out of whack. If so, then I might get somewhere by either understanding the >> app registry better or understanding what DEBUG does. >> >> Any thoughts? >> > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/fb61e2e6-001b-407c-b966-a3c1dc203a59%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/fb61e2e6-001b-407c-b966-a3c1dc203a59%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWpryMyyy5xji4NtgYUAZg0NYu1mpRt_LAqfdhtCy8xO8w%40mail.gmail.com.
