Using Cascade to Publish Server Side Code


Notes on using cascade to publish server side coding

General observations

  1. When placed in a page, server side code must be wrapped within a cascade element <!--#START-CODE code #END-CODE--> for the page to pass validation. see HH's documentation.
  2. Some coding languages, .NET, most noteworthy, require a statement at the top of the page. To add this, wrap the code with <!--#START-ROOT-CODE code #END-ROOT-CODE--> and add it to the <head> section of your page. When Cascade renders the page it will place that code at the top of the page. See HH's documentation.
  3. Cascade will not allow HTML comments to be nested. Apparently to enforce this, Cascade's HTML validator will not allow a double dash within a comment element. Where this becomes problematic is when you wish to use '--' within the #START-CODE element in point 1 above. You will not be able to use HTML comments ( <!-- comment --> ) within the START-CODE element.
    • It is possible to use html comments if you end your #START-CODE element, include your HTML comment, then start a new #START-CODE section.
    • Coldfusion users, take note of point 1 in the Coldfusion section.

Coldfusion

  1. In light of Cascade's rejection of double dashes, (see #3 in the general section) In my experience, CF comments ( <!--- comment ---\> ) became totally unusable. Not only could they not be nested inside the #START-CODE element, but would not validate outside of the #START-CODE either. Apparently it has to do with how the validator sees the triple dash ( --- ) in CF's comment structure.

PHP

  1. Quotes

.NET

#top

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'ivy-ai' is unknown.