Closed z-siddiqi closed 4 years ago
I was checking the custom error pages on the live website, and to my surprise got the Django error page instead (see image). Production settings seem to have DEBUG=False so not really sure why this happens.
Yes, there was an issue with the productions settings where there was a duplicate DEBUG = True
. It has since been fixed, however, the live site hasn't been setup with the new docker deployment process since we are thinking of migrating it from Heroku to Digital Ocean.
I was checking the custom error pages on the live website, and to my surprise got the Django error page instead (see image). Production settings seem to have DEBUG=False so not really sure why this happens.
Yes, there was an issue with the productions settings where there was a duplicate
DEBUG = True
. It has since been fixed, however, the live site hasn't been setup with the new docker deployment process since we are thinking of migrating it from Heroku to Digital Ocean.
That makes sense, thanks for explaining.
I was checking the custom error pages on the live website, and to my surprise got the Django error page instead (see image). Production settings seem to have DEBUG=False so not really sure why this happens.