okay, but it's even harder to guess what is a problem there without ability to see relevant code pieces. btw, you may want to check this https://www.geeksforgeeks.org/important-differences-between-python-2-x-and-python-3-x-with-examples/#Unicode as you most probably had to migrate python as well
On Wednesday, October 16, 2019 at 6:39:53 PM UTC+3, Boris Romero wrote: > > Thanks for the answer Lemme! As I said, my problems appear exactly when I > update django from 1.11 to django 2.2.x. With this change a lot of > libraries need to update, and now I was trying to remove some of them and > proving if they are the reason of this strange behavior. Before update > django, all works perfectly. > > Libraries who update with djnago 2.2.x are: channels, daphne, attrs, > django-allauth, djnago-crispy-forms, djnago-extensions, django-taggit, > psycopg2, djangorestframework, and subdomains (using a pull request for > compatibility). > > The problems happens with DEBUG=False, and using nginx and uwsgi, using > the same configuration for django 1.11 and django 2.2.x > > Greetings! > > On Wednesday, October 16, 2019 at 8:59:21 AM UTC-3, lemme smash wrote: >> >> it's really hard to help here without understanding whats going on there. >> when i ask for example I meant not only piece of page screenshot to see >> what you mean, but whole stack of how you pass data in a view and how you >> render it in a template >> >> On Tuesday, October 15, 2019 at 9:31:26 PM UTC+3, Boris Romero wrote: >>> >>> 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/cd732510-2dd6-47ba-a939-9aa28e357ed0%40googlegroups.com.
