#32016: mail_admins handler cannot be configured.
-------------------------------------+-------------------------------------
Reporter: Susana Cárdenas | Owner: (none)
Molinar |
Type: Bug | Status: closed
Component: Error reporting | Version: 3.1
Severity: Normal | Resolution: needsinfo
Keywords: settings, logging | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Susana Cárdenas Molinar):
Replying to [comment:1 felixxm]:
> Thanks for this ticket, however this configuration works for me with
Django 3.1. Can you provide a small project that reproduces the issue?
(without unrelated handlers, loggers, etc.).
It looks like the error is not the `mail_admins` rather that the
`SECRET_KEY` is improperly configured. This was working before in Django
2.2 and 3.0. Do I need to make any changes to the settings file?
This is the error I am getting before the mail_admins error:
{{{
raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must
not be empty.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32016#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates/067.badbf0cd0d31c46bd1373e1633fb3c94%40djangoproject.com.
