Skip to content
This repository has been archived by the owner on Oct 29, 2019. It is now read-only.

Lead content rendered as HTML verbatim #433

Open
FabriceSalvaire opened this issue Oct 18, 2016 · 6 comments
Open

Lead content rendered as HTML verbatim #433

FabriceSalvaire opened this issue Oct 18, 2016 · 6 comments

Comments

@FabriceSalvaire
Copy link

FabriceSalvaire commented Oct 18, 2016

For some reason the lead content of edited articles is rendered as HTML verbatim.

A server restart solved the issue.

@yboussard
Copy link

I have the same issue !
capture d ecran 2016-10-19 a 17 20 31

@kirimi
Copy link

kirimi commented Nov 7, 2016

I also have the same issue. Uwsgi restart solves the issue.

@jpVm5jYYRE1VIKL
Copy link

jpVm5jYYRE1VIKL commented Nov 18, 2016

Issue not uwsgi related. I have the same if even i use runserver . After some time issue disappear.
Issue appear after every new blog page added

@maartinez
Copy link

maartinez commented Nov 25, 2016

Same here. Tested on runserver. It happens every time I add new article. But after few minutes when I refresh the page, even without restarting the server, everything is back to normal...

Edit:
In aldryn_newsblog/templates/aldryn_newsblog/includes/article.html I changed this line:
{% render_model article "lead_in" %}
to:
{{ article.lead_in|safe }}
and now it looks like it's working.

@johnwoltman
Copy link

I'm seeing the same issue. The solution from @maartinez works, but removes the "click to edit" feature from the lead-in.

@sonic182
Copy link

Same issue here

image

maybe the implementation of render_model is doing it wrong. Could be fixed with more parameters I think. A djangocms issue then.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants