Blog Sections Open
Showing [[Ditto]] or Other Evo Tags as Literal Text
Documentation pages and cheat sheets often need to show Evo tags as examples, not as live parser instructions.
When you write documentation or examples inside Evolution CMS, parser tags such as or Showing or Other Evo Tags as Literal Text can accidentally execute instead of rendering as text.
Typical Use Cases
- Documentation pages
- Training content for editors or developers
- Reference articles that need to show snippet calls verbatim
Safe Strategies
- Escape the brackets before output.
- Wrap examples in code blocks that bypass parser execution.
- Store examples in a way that avoids a second parser pass.
The key is to decide early whether the page is instructional content or runtime content. Once you mix the two carelessly, code examples become parser input.
Newer post
Choosing ACE or CodeMirror for Editing Templates in Evolution CMS
A practical comparison of code editors for template editing and why TinyMCE is usually the wrong tool for real template work.
Older post
Writing JotX Comment Data into a Separate Database Table
A practical way to capture selected JotX comment fields for CRM, mailing, or reporting workflows.