-
Notifications
You must be signed in to change notification settings - Fork 657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors logged #1058
Comments
I'm experiencing the same issue, were you able to resolve it? |
So far i'm stuck with silencing the logs. |
I'm able to reproduce this with when DEBUG is True (but not when it is False). But yes, if we try to resolve a variable which does not exist an exception is thrown. But that's intended behaviour, isn't it? https://docs.djangoproject.com/en/5.1/ref/templates/api/#how-invalid-variables-are-handled |
Well in that case we should not try to get invalid variables in DEBUG. |
Seems acceptable to me, but I see your point. So if someone wants to send a pull-request, we'll take a look at it. |
/templates/admin/base.html
/templates/admin/change_list.html
|
@sehmaschine django grappelli it's greatest ever job over django admin panel. |
When accessing the admin page, we currently have a bunch of errors logged:
This currently happens in a completely new project with nothing installed and no code. All I did was install grappelli. Without grappelli, no error is logged.
Settings:
It doesn't look like it's breaking anything but it's clogging our logs and besides, having lingering exceptions is never a good thing.
Ofc, adding the following silences the exceptions since they are at the DEBUG level:
Still, I would prefer not having to silence the template errors altogether just because I'm using the grappelli package.
The text was updated successfully, but these errors were encountered: