6

I've been working on a custom page in Sitecore over the holidays, and I've noticed an issue where Sitecore removes JavaScript lines from the editor.

Here's an overview of my current scenario:

  1. I add Javascript to the page.
  2. I save, check in, and publish.
  3. Changes are there, and everything is working.
  4. I work on it later and those changes are no longer there.

I'm the only one who's edited this page, and it is publishing the current/correct version. It doesn't matter if I add the script through the "Show Editor" or "Edit HTML" features of the content editor. It only removes the JavaScript though; all of my other changes are intact.

Is there something that I'm missing about Sitecore's implementation of JavaScript? I'm not sure what else to do in order to diagnose it, so I was hoping someone here would have an explanation for this.

Richard Seal
  • 4,248
  • 14
  • 29
Tyler Corbett
  • 63
  • 1
  • 3

2 Answers2

15

Removing the script-tags in the RTE in Sitecore is standard behavior when the item is saved. However, in Sitecore 6.4.1 rev. 120113 and Sitecore 6.5 Update-4 there is a new property added in the web.config:

<setting name="HtmlEditor.RemoveScripts" value="true"/>

Setting this value to false should solve your problem. If you are using an older version of Sitecore, take a look at this blogpost which shows a workaround for older versions.

Community
  • 1
  • 1
Martijn van der Put
  • 4,062
  • 1
  • 18
  • 26
3

Are you adding this javascript in a Rich Text Editor?

I've seen the rich text editor strip out javascript as it saves. We have typically added javascript blocks in as a separate sublayout pulling from a multi-line text field and having it render out directly, rather than editing javascript through the rich text editor.

Jay S
  • 7,904
  • 2
  • 39
  • 52
  • That's what we thought at first, but this behavior happens in both editors: the HTML tab on the Rich Text Editor as well as the Edit HTML plain text editor. Thanks for your reply! – Tyler Corbett Jan 07 '13 at 14:29
  • @Jay Did you find a solution to it? Could you support your answer through screenshots – Siddhi Kamat Jun 13 '22 at 14:09
  • 1
    @Sidso: I'm sorry, but this was almost a decade ago... I don't have anything from that time anymore. My very rough memory of how we avoided this was to have users put JavaScript into a separate field, not a Rich Text field. However, there have been a LOT of changes in the platform between 2013 and now. – Jay S Jun 14 '22 at 10:51