Open dqd opened 4 hours ago
The workaround is to add NAME
to TEMPLATES
setting, like here:
TEMPLATES = [
{
"NAME": "django", # <-- added
"BACKEND": "django.template.backends.django.DjangoTemplates",
"DIRS": [],
"APP_DIRS": True,
"OPTIONS": {
"context_processors": [
"django.template.context_processors.debug",
"django.template.context_processors.request",
"django.contrib.auth.context_processors.auth",
"django.contrib.messages.context_processors.messages",
],
},
},
]
According to the Django documentation, NAME
is optional (it defaults to the name of the module defining the engine class), so I still think this is a bug.
Hello and first of all, thank you for your great Django SSO plugins.
After I installed
django_google_sso
anddjango_github_sso
together on the latest version of Django 5.1, I got W003 warnings. As described in the documentation, this is expected and I should use this setting to silence original Django check and run an alternate check:However, when
SSO_USE_ALTERNATE_W003
is set toTrue
, the app crashes for me:It looks like a bug to me.