Bug #23308 Bug Fixed

Fields storing HTML escape the HTML in the template

Version: 4.0.0 Reporter: Jeremy Gimbel - Conflux Group

I’ve noticed this in RTEs, textareas and text inputs, with the formatting set to none or xhtml.

Adding the :raw_content filter removes the escaping, however it seems like the desired behavior for a field intentionally storing HTML (especially the RTE) should be to output unescaped content by default.

  • Hi Jeremy, sorry for your trouble! Yes this sounds like a problem, would definitely like to get it fixed. HTML in a text-based fields is rendering fine for me though. When you say escaped, do you mean the HTML brackets are encoded as entities? Is this a new install or upgrade? Is it specific to fields inside a Grid or Fluid field?

    Kevin Cupp
    08th December, 2017 at 11:09am
  • This was a brand new install, with just standard text, textarea and RTE fields added directly to the channel, not inside a Grid or Fluid field.

    By escaped I mean that when you load the page in the browser it comes up as

    Some text instead of actually rendering the paragraph.

    I realize now that this is probably a result of the HTML Formatting setting on the channel, but it seems like at least for an RTE field, that setting should be ignored, or maybe it’s really not necessary at all since each field has its own formatting settings anyway.

    Jeremy Gimbel - Conflux Group
    08th December, 2017 at 11:27am
  • That should have been:

    Some text
    Jeremy Gimbel - Conflux Group
    08th December, 2017 at 11:28am
  • Haha or not. (The p tags are showing in the rendered page)

    Jeremy Gimbel - Conflux Group
    08th December, 2017 at 11:28am
  • Ah yes it looks like the default for HTML formatting is to convert all HTML into entities, which was a mistake. It actually looks like many of the intended defaults for channel settings aren’t getting set properly, side effect of having everything on one form now. We’ll get that fixed up then which should in turn fix this issue, at least for any new channels created after we ship the fix, for now you’ll just have to change the setting on existing channels. Sorry again for the trouble and thanks for your help on this!

    Kevin Cupp
    08th December, 2017 at 1:40pm

You must be signed in to comment on a bug report.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases