Blog Sections Open

Fixing Escaped Quotes in JotX Comment Output

Why JotX comments can start showing backslashes before quotes and what to normalize before rendering comment text.

If a comment suddenly renders as \"text\" instead of plain quotation marks, the problem is usually not the template itself. It is a mismatch between how comment data is stored, escaped, and printed on the page.

In older comment setups this often comes from data being escaped twice: once before storage and again before output. The result is visible backslashes in perfectly normal comments.

What to audit

  • Check whether input is passed through addslashes-like logic before save.
  • Check whether the output template also escapes already-slashed data.
  • Verify the comment field encoding and the output filter chain.

The correct fix is to normalize escaping at one stage only. Store clean text, then escape only as needed for safe HTML output. Once comments are escaped in two different layers, small punctuation problems turn into ugly public output.

Comment systems feel reliable only when they treat stored text and rendered text as two separate responsibilities.

Newer post

Fixing the “Refused to Set Unsafe Header Connection” Manager Bug

What to check when saving a resource leaves the right manager pane blank and the browser console reports an unsafe Connection header.

Older post

Restoring the Blank Resource Editor in Evolution CMS

What to check when documents open to a blank editing pane while chunks, snippets, plugins, and templates still edit normally.