I'm trying to update template code on a EE site I inherited and whenever I save the template, after making my changes, the HTML formatting gets all screwed up and the JS is completely stripped out. For example, almost all of the HTML carrots are turned into:

< and >

And the JS is just:


Even if I don't make any changes to the code and just save the template in the inline editor this happens - new to EE and trying to figure out what's causing this. EE version 2.2.1, Wygwam 2.3.2... no other obvious add-ons that might cause issues to me. I found the protect_js config option and set it to 'y' (wasn't previously included) but it doesn't seem to make a difference. If I inspect the actual editor element I see a bunch of classes for markItUp - is that normal?

  • Is upgrading the site an option?
    – CreateSean
    Sep 10, 2013 at 15:32
  • I'm not sure yet if the client has the license or the previous developer but I will find out.
    – Bjorn
    Sep 10, 2013 at 15:50
  • 1
    For what it's worth, I have never seen this in 8 years working with EE. This has to be caused by an EE addon or a browser addon. Can you post a screenshot of the template edit field? I'd like to see if an addon is being used to format the template code.
    – Anna_MediaGirl
    Sep 10, 2013 at 18:18
  • Well good, at least I'm not losing my mind then. It's happening on the live server and in a dev environment. It looks like I am able to just edit the actual template files, which I'd prefer anyway, but this just seems really odd and I'm wondering if there are other issues with the site. i.imgur.com/2nbwQZj.jpg
    – Bjorn
    Sep 10, 2013 at 19:07

3 Answers 3


This sounds very similar to another post, Characters are being re-encoded in control panel.

Check in your system/expressionengine/config/config.php file. Do you have $config['global_xss_filtering'] set to TRUE?

It should look like this in your config file:

| Global XSS Filtering
| Determines whether the XSS filter is always active when GET, POST or
| COOKIE data is encountered
$config['global_xss_filtering'] = FALSE;
  • That was it! Thanks a lot I was really stumped.
    – Bjorn
    Sep 11, 2013 at 17:11

From the source shot, it looks like MarkItUp may be the issue, trying to turn the template editor into a wysiwyg


You mention Wygwam which means an entry, not a template... can you confirm exactly where you are seeing this behavior?

If you're doing this via the Control Panel - then can you try making those template updates via FTP? I suspect that there is some server thing, similar to mod_security (or mod_security itself, though that is usually has different symptoms).

If you can make your template updates via FTP, then look at form submissions and server security for sure. You'll need to save templates as files before you can try this.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.