Blog Sections Open
Stripping HTML Tags from Resource Content Safely
Use output modifiers to turn HTML-rich resource content into plain text for XML feeds and clean exports.
When you build an XML feed with DocLister, raw HTML from the content field is rarely what you want. Feeds, exports, and third-party parsers usually need plain text on a single line.
The original question was simple: can [+content+] be rendered without HTML tags? The answer is yes. The practical solution is to apply output modifiers before the content lands in the XML template.
Simple output cleanup
[+content:strip_tags+]
If your output must also become a single line, combine tag stripping with whitespace cleanup in the template or prepare the value before rendering.
[+content:strip_tags:trim+]
When XML feeds need stricter cleanup
For product feeds and marketplace exports, stripping tags is usually only the first step. You may also want to collapse line breaks, decode entities, or limit the length of long descriptions.
[+content:strip_tags:replace=`
== `:replace=`
== `:trim+]
A safer feed pattern
If the same document description is used in many exports, prepare a dedicated short plain-text field instead of cleaning the full HTML body every time. That gives you better control over length, punctuation, and feed quality.
Practical SiteContent Model Examples in Evolution CMS
Modern Evolution CMS examples for querying SiteContent with TVs, tree methods, sorting, and breadcrumb-style lookups.
Updating Parent Fields When Child Resources Change
A practical pattern for aggregating child TV values back into a parent resource so filters and listings stay fast and consistent.