tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/20587-cascade-fiddles-with-my-include-in-html-commentsCascade CMS: Discussion 2018-10-18T20:37:46Ztag:help-archives.hannonhill.com,2010-02-09:Comment/385505422015-11-25T13:48:47Z2015-11-25T13:48:47ZCascade fiddles with my "include" in HTML comments<div><p>Hi,</p>
<p>Cascade expects there to be a <code><head></code> tag
within the Template for HTML outputs in order for it to generate
the inline editing region resources and markup. If you leave out
the <code><head></code> tag, Cascade will attempt to re-write
the Template.</p>
<p>Based on the snippets you provided, I suspect this may be the
issue you are running into here. When you have a moment, try adding
in the <code><head></head></code> tags to see if that
resolves at least some of the rewriting behavior you are
seeing.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/385505422015-11-25T18:41:46Z2015-11-25T18:41:46ZCascade fiddles with my "include" in HTML comments<div><p>Thanks Ryan. I'm sorry, I've created confusion by raising four
related issues in one post. Let me focus on the two really
troubling matters -- one involving blocks, one involving placement
in a template of an HTML comment (that invokes a server-side
include directive).</p>
<ol>
<li>A Cascade block with just this content:</li>
</ol>
<pre>
<code><!--#include virtual="somefile.inc"--></code>
</pre>
<p>called from a template region emits this HTML:</p>
<pre>
<code><br/><!--#include virtual="somefile.inc"--></code>
</pre>
<p>It's wrong. But I'm guessing there's a workaround.</p>
<ol>
<li>And second, wherther Cascade renders "include" HTML comment at
all (just like the one shown above) depends on <em>where</em> it's
placed within the head section of the HTML template. Note the two
cases illustrated in my OP.</li>
</ol></div>burleightag:help-archives.hannonhill.com,2010-02-09:Comment/385505422015-11-25T21:20:17Z2015-11-25T21:20:17ZCascade fiddles with my "include" in HTML comments<div><p>My apologies for the confusion there, thank you for
clarifying.</p>
<p>Are you using an XHTML Block by chance? If so, there is a known
issue with TinyMCE in which the WYSIWYG will insert a
<code><br/></code> tag if there is no root element/tag. I
believe this only occurs with Firefox, but I could be mistaken.</p>
<p>My suggestion would be to use an XML block instead to avoid
TinyMCE all-together. This would also make updating easier since
you can actually see the content as opposed to the "hidden" HTML
comment.</p>
<blockquote>
<p>And second, wherther Cascade renders "include" HTML comment at
all (just like the one shown above) depends on where it's placed
within the head section of the HTML template. Note the two cases
illustrated in my OP.</p>
</blockquote>
<p>Just to clarify, are the code snippets the expected result when
rendering a page, or is this what you are entering within the
actual template?</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/385505422015-12-01T13:58:05Z2015-12-01T13:58:05ZCascade fiddles with my "include" in HTML comments<div><p>Ryan:</p>
<ul>
<li>
<p>Yes, the block was XHTML. Since it included only an HTML comment
embedding a server side directive there's no content for the
WYSIWYG editor to render. The added break was seen in Firefox and
Chrome.</p>
</li>
<li>
<p>Notice that para is in past tense? Rather than continue to
struggle, I recreated the block as a text block, and now there are
no problems.</p>
</li>
<li>
<p>Yes, the template is HTML; what I showed in the OP was verbatim
from the template.</p>
</li>
</ul></div>burleigh