2👍
✅
So here is what i think is happening here. If i’m right in saying that you are navigating to /accounts/login first.
When you go to /accounts/login django uses your authentication view which just renders the html without creating a form. This is why you don’t see the fields initially.
The form is setup to submit to /login/ because action is set to “{% url ‘thirdauth:login’ %}”. /login/ is using the default django login view. So once you sumbit the form with no fields this causes an error in the defualt view which redirects you back to /login/. This is why you then see the fields with the “this field is required” errors after clicking submit.
Hope that explains it
Source:stackexchange.com