Yea, I disconnected that feature on my phone.
*“None of you has faith until he loves for his brother or his neighbor what
he loves for himself.”*
On Mon, Jan 1, 2018 at 7:03 PM, James Schneider
wrote:
>
>
> On Jan 1, 2018 6:01 PM, "Malik Rumi"
On Jan 1, 2018 6:01 PM, "Malik Rumi" wrote:
I'm sorry, James. What the heck is 'steering' in this context?
It's not, my phone auto corrected it to steering. It was supposed to be
'string'.
--
You received this message because you are subscribed to the Google Groups
Mike,
Thank you, I think we are now on to something. I've heard of bleach, but
never used it and frankly forgot about it until now. I will go read up on
it. I also have never heard of Django's own mark_safe, so I will check that
out, too.
I did a little more experimenting with autoescape while
I'm sorry, James. What the heck is 'steering' in this context?
*“None of you has faith until he loves for his brother or his neighbor what
he loves for himself.”*
On Mon, Jan 1, 2018 at 3:11 PM, James Schneider
wrote:
>
>
>
> Have you verified that object.content
On 2/01/2018 10:01 AM, Malik Rumi wrote:
I even tried putting this at the top of my detail template, inside {&
block content %}:
p }
p {
Have you verified that object.content contains un-escaped (raw) HTML? Is it
possible that the steering is being escaped before it is saved?
s/steering/string/
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and
On Jan 1, 2018 2:29 PM, "Malik Rumi" wrote:
Well, as I said at the beginning, I don't seem to 'get' autoescape and
safe. For example, I put this in my template:
{{ object.content|linebreaks|safe }}
But the result in my web page is:
Friday, November 17, 2017
Have
I even tried putting this at the top of my detail template, inside {& block
content %}:
p }
color: red;
}
But the result was the same:
This is all just to help me understand. I put this
So what am I doing wrong, here?
*“None of you has faith until he loves for his
This also fails, and renders exactly as you now see it on my web page:
{% autoescape off %}
Yea, that's going to be a monster
{% endautoescape %}
*“None of you has faith until he loves for his brother or his neighbor what
he loves for himself.”*
On Mon, Jan 1, 2018 at 2:28 PM,
Well, as I said at the beginning, I don't seem to 'get' autoescape and
safe. For example, I put this in my template:
{{ object.content|linebreaks|safe }}
But the result in my web page is:
Friday, November 17, 2017
5:36 pm
pga4 and mezz
I am happy to report.
So what
Hi.
By default all strings processed through Django templating language are
considered as unsafe. IOW all strings gets HTML escaped properly.
To get around that you can either use safe filter or declare particular
string as a safe in a view.
1.1.2018 20.47 "Malik Rumi"
Hi Malik,
I share your views regarding the autoescape templatetag.
Personally I don't use the Django template framework but depends on Mako
for UTF-8 template rendering and HTML escaping.
Happy new year!
Etienne
Le 2018-01-01 à 13:46, Malik Rumi a écrit :
Apparently I completely
Apparently I completely misunderstand the built in template tags {%
autoescape &} and {% safe %}. Either they don't do what I expect, or I
can't get them to do what I expect. But what I am trying to do is not at
all unusual, so this post is all about learning from the community what are
the
13 matches
Mail list logo