tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/19042-marking-that-a-node-contains-html-in-xmlCascade CMS: Discussion 2015-08-27T20:16:36Ztag:help-archives.hannonhill.com,2010-02-09:Comment/376514942015-08-13T16:36:23Z2015-08-13T16:36:23ZMarking that a node contains HTML in XML<div><p>Greg-</p>
<p>I assume you are generally going to be just outputting the
wysiwyg contents and not further parsing it as the structure may
not be consistent. If you are looking to further parse the contents
of the wysiwyg contents then I would wager that is probably not the
best field type.</p>
<p>If you just want to output the contents of the wysiwyg field you
can do the following:</p>
<p>Unless I am misunderstanding what you are trying to accomplish
that should do it.</p>
<p>-Matt</p></div>mdcartertag:help-archives.hannonhill.com,2010-02-09:Comment/376514942015-08-18T00:14:29Z2015-08-18T00:14:29ZMarking that a node contains HTML in XML<div><p>Hey:</p>
<p>Good idea, but not quite what I need.</p>
<p>The problem is that parsers assume that the text in the WYSIWYG
nodes is actually XML. So, if I want to convert it to JSON, for
example, I get something like this (using the example XML from
above):</p>
<pre>
<code>{
"description": {
"p": {
"#text": [
"What's ",
" with ",
"?"
],
"strong": "up",
"em": "that"
}
}
}</code>
</pre>
<p>Not really ideal.</p>
<p>Using a transform to wrap certain fields in CDATA tags in
Cascade seems to be working, though. However, doing things that way
also seems to violate XML standards. But it does work.</p>
<p>Thanks!<br>
Greg</p></div>Greg Gomez