Yes, this error is from our development server and we have DEBUG = True. Thanks for quick answer. We will not turn this on in production server.
Best regards, ~Ram On Sun, Jul 12, 2020 at 8:18 PM Christophe Pettus <x...@thebuild.com> wrote: > > > > On Jul 12, 2020, at 19:08, Ram <ram.mullap...@gmail.com> wrote: > > > > If coding needs to be changed here to avoid stack trace on the user > browsers, what should be changed here? > > You have DEBUG = True; that will result in the debugging output you see. > You shouldn't ever have it turned on for a production website. > > -- > -- Christophe Pettus > x...@thebuild.com > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/0BCA3B5B-7C4E-4D94-89DE-7B94A5C4B201%40thebuild.com > . > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2BOi5F0o%3DM%2Bheh5nc%2BeuWJZVG-7YPzZo4pJHV%3DNXS78%3DqbGMkA%40mail.gmail.com.
