Any help or ideas? Thanks! On Thursday, October 10, 2019 at 12:15:42 PM UTC-3, Boris Romero wrote: > > Hi! Yes, it's reproducing when I run it locally, but with DEBUG=FALSE and > with nginx and uwsgi. And no, it's not a database encoding problem, it just > involves the templates, because the same database, with diferents instances > of the app (with the upload and without it) not make any differences. > > Thanks for the ideas! > > > On Thursday, October 10, 2019 at 11:38:48 AM UTC-3, lemme smash wrote: >> >> so, it's not reproducing when you run it locally? >> also, can you provide an example of string where you have "strange" >> character? most probably you store it in database. >> >> On Thursday, October 10, 2019 at 1:48:52 AM UTC+3, Boris Romero wrote: >>> >>> Hi! >>> >>> I recently update Django from 1.11 to 2.2.6 and I have a serious problem >>> with the templates rendering when i put on production my site (Nginx + >>> uWSGI + Django). The problem is a lot of '/n' and strangers characters that >>> appears when I render any page, that obviuosly suggest is a encoding >>> problem, but I can't find the exact configuration problem. It just happen >>> when the app is deployed, that is, when DEBUG = False. >>> >>> Any help? >>> >>> Thanks! >>> >>
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/aca345e4-33ef-47d4-b792-42f560c7004b%40googlegroups.com.
