• This has been happening for a while and I’ve tried googling but how do you google < ? pointy brackets, chevrons, whatever. I tried putting one into the subject line and it vanished. I can’t even put the proper string in this post because > just turns into >

    Anyway. If I put these <> into a post, usually it turns out OK, but if you then edit that post (as we frequently do with our local wordpress install) then the <> get turned into &am p;lt; or &am p;gt; We’ve tried using
    pre and code tags` and we currently have the crayon code plugin but it keeps doing it. Our posts often contain code or configs so we need to use < and >.

    Can anyone point me in the right direction?`

Viewing 6 replies - 1 through 6 (of 6 total)
  • All such characters are automatically stripped from Post and Page titles by WordPress core for reasons of security. I strongly recommend that you do not do anything to change this as you may open a security hole for hackers to use.

    Thread Starter vmos

    (@vmos)

    This is an internal installation, only a few people can see it and even fewer can post to it, so we’re not that worried about security.

    This wasn’t always a problem though, we moved the wordpress instance a few months back and it left the <> alone when it was on the old server.

    The old server was debian and the new one is ubuntu, but I’m not sure which part of the change has caused this. Something in the php ini perhaps?

    Not as far as I know. I’m pretty sure that all titles are run through a striptags and encoding filter by WordPress core.

    Thread Starter vmos

    (@vmos)

    all titles? But this is happening in the body, even within code tags. Aren’t the pre and code tags supposed to mean that the formatting doesn’t get messed with?

    Sorry – I meant all Post & Page titles as entered via the WP backend.

    vmos, did you ever come up with a solution to your conversion issue? I’m having a similar problem…

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘How do I stop pointy brackets turning into & amp ; lt;’ is closed to new replies.