Debug=False breaks Django/MM3-Login-page
Hi folks,
I'm trying to hide the custom 404 error messages from Django.
Page not found (404) Request Method: GET Request URL: http://......./non-existent-2008020390
Using the URLconf defined in mailman_web.urls, Django tried these URL patterns, in this order:
mailman3/
archives/
^user-profile/delete$ [name='mm_user_account_delete']
^user-profile/$ [name='mm_user_profile']
accounts/
admin/
postorius/
hyperkitty/
The current path, non-existent-2008020390, didn’t match any of these.
You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.
Switching DEBUG=True (currently set in settings.py) to false does indeed hide additional debugging output, but following pages are not accessible anymore (Server Error).
user-profile/ accounts/logout/ hyperkitty/
Switching back to DEBUG=True brings back accessibility.
This is
Mailman Core-Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
any help is greatly appreciated.
Thank you.
Stefan
On 10/15/24 02:02, Stefan Bauer via Mailman-users wrote:
Switching DEBUG=True (currently set in settings.py) to false does indeed hide additional debugging output, but following pages are not accessible anymore (Server Error).
user-profile/ accounts/logout/ hyperkitty/
I don't understand why the DEBUB setting would affect this, but in any case, what's in the mailman web logs for these Server Errors?
This is
Mailman Core-Version GNU Mailman 3.3.9 (Tom Sawyer)
Installed how?
Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro
-
Stefan Bauer