tag:help-archives.hannonhill.com,2010-02-09:/discussions/bug-reports/2728-compare-to-current-with-style-tags-issueCascade CMS: Discussion 2015-11-02T20:07:09Ztag:help-archives.hannonhill.com,2010-02-09:Comment/378983452015-09-11T13:41:36Z2015-09-11T13:41:36ZCompare to Current with <style> tags issue<div><p>Hi Jason,</p>
<p>The self-closing <code><style></code> tag behavior you are
running into is due to a process used during XML serialization that
expands specific tags. Specifically, there is a configuration file
that determines what tags should be left expanded; otherwise, the
tag will be converted to a self-closing tag. This is because XML
has no notion of HTML tags that are not meant to be
self-closing.</p>
<p>We have <a href="https://hannonhill.jira.com/browse/CSI-832">a
known defect logged</a> for this behavior. Feel free to use this
link to track the progress of this issue or keep an eye out for it
on our <a href="http://www.hannonhill.com/kb/Release-Notes">Release
Notes site</a>.</p>
<blockquote>
<p>Is there a way for us to be able to turn off the HTML Comment
tags or configure the system not to have the XML Parser reduce the
style tag to self-closing? Thanks.</p>
</blockquote>
<p>Unfortunately, there is nothing you could do from within Cascade
to change this other than perhaps trying to surround the
<code><style></code> tag with a <code>#protect</code> code
section, to see if the serialization leaves it. I'm not 100% sure
it will, though.</p>
<p>That being said, if you would like a temporary workaround for
certain tags, let me know and I can provide you with steps to
update the configuration file I mentioned with tags you wish to be
left alone and we can see if that helps out. The downside here is
these changes would need to be re-added after each upgrade since
the file would be overwritten by the update.</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/378983452015-09-11T14:16:09Z2015-09-11T14:16:09ZCompare to Current with <style> tags issue<div><p>Greetings Ryan,</p>
<p>Yes, the instructions would be highly useful, even if they would
need to be redone during an upgrade. There aren't many content
editors adding in style tags, but the ones that are tend to edit a
large number of pages and across multiple sites. In addition,
Compare to Current has become essential in our workflows as our
content checkers can focus specifically on the areas where changes
occur. Previously they had to switch back and forth between Current
and Working Copy or snag the HTML of the two and run it through
WinMerge.</p>
<p>Cheers,</p>
<p>Jason Verschage</p>
<hr></div>jason.verschagetag:help-archives.hannonhill.com,2010-02-09:Comment/378983452015-09-11T17:12:42Z2015-09-11T17:12:42ZCompare to Current with <style> tags issue<div><p>Sounds good, Jason, definitely worth a shot.</p>
<ul>
<li>Stop Cascade</li>
<li>On the application server, edit
<code>tomcat/webapps/ROOT/WEB-INF/classes/com/hannonhill/cascade/xml/output/expanded-elements.xml</code></li>
<li>Add a new entry for the <code>style</code> tag:
<pre>
<code><element-name>style</element-name></code>
</pre></li>
<li>Start Cascade</li>
<li>Attempt to reproduce the behavior to see if the change fixes
the issue</li>
</ul>
<p>Note: as I mentioned, these steps will need to be re-applied
after any update because this file is replaced during the
upgrade.</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/378983452015-09-24T12:40:31Z2015-09-24T12:40:31ZCompare to Current with <style> tags issue<div><p>Hi Jason,</p>
<p>Just wanted to follow up to see if you had a chance to view my
<a href="http://help.hannonhill.com/discussions/bug-reports/2728-compare-to-current-with-style-tags-issue#comment_37907776">
recent comment</a>. If you were able to follow the steps, did they
resolve the issue you were encountering?</p>
<p>Please let us know if you have any questions.</p>
<p>Thanks.</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/378983452015-09-24T13:05:36Z2015-09-24T13:05:36ZCompare to Current with <style> tags issue<div><p>Apologies for not responding sooner.</p>
<p>We did update our test server by making the configuration
update. The good news is that It no longer collapses the style to a
single tag, so the page doesn't break. However, on Compare to
Current, the style seems to be removed completely. So, if the only
thing changed by a content editor is the style, there's no
indication on the page. We haven't yet met with Web Team Management
to discuss moving the change to production and if the partial
solution is satisfactory, but at the very least standard content
changes are viewable.</p>
<p>Cheers,</p>
<p>Jason</p>
<hr></div>jason.verschagetag:help-archives.hannonhill.com,2010-02-09:Comment/378983452015-10-05T12:27:57Z2015-10-05T12:27:57ZCompare to Current with <style> tags issue<div><p>Hi Jason,</p>
<p>Just wanted to follow up to see if you had a chance to speak
with your team to discuss whether the fix will suffice. Curious,
but if you scope out the source code of the comparison, does the
<code><style></code> tag contain any additional markup?</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffith