Hi! I discover this problem start with Django 2.1, Django 2.0.13 still
working good. I'm reading the changes on Django 2.1 whom can cause this
problem. Thanks for the ideas!
On Wednesday, October 16, 2019 at 4:35:36 PM UTC-3, Boris Romero wrote:
>
> Thanks again for the answer. I b
-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 exactl
nly 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,
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 templa
t;
> 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
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
6 matches
Mail list logo
