CMS 10.6.378: Orphaned DITA Aliases Generated Under Map Group Elements
In a DITA map's alias structure, CMS 10.6.378 generates orphaned aliases for child mapref and topicref elements nested under map group (container) elements. These aliases are orphaned because the CMS does not generate aliases for the parent topichead, topicset, or topicgroup element.
Statement of Issue
When creating or updating a DITA map's alias structure, CMS 10.6.378 does not generate aliases for map group elements (i.e., containers), including <topichead>, <topicset>, and <topicgroup>. Instead, the CMS generates aliases for child <mapref> and <topicref> of these elements, resulting in orphaned aliases in the Site Tree. The published alias navigation excludes these orphaned child aliases.
Resolution
For <topichead> elements without an @id attribute or <navtitle> and for <topicgroup> and <topicset> elements, the CMS only generates aliases for their children and not for the map group elements. These child aliases are included in the alias structure and navigation. They are not orphaned.
For <topichead> elements that contain an @id attribute and a @navtitle element, CMS 10.6.492 generates an alias for <topichead> in addition to aliases for its children. When published, both are included in the navigation.
For example:
<topichead id="topichead1" navtitle="Resources">
<topicref href="../../stylesheets/_presentations_/FormField_Button.xsl" type="concept">
<topicref href="../../stylesheets/_presentations_/FormField_Captcha.xsl" type="concept" />
<topicref href="../../stylesheets/_presentations_/FormField_Checkbox.xsl" type="concept" />
<topicref href="../../stylesheets/_presentations_/FormField_Label.xsl" type="concept" />
</topicref>
</topichead>
In the Site Tree, the aliased <topichead> document type information tag displays as DITA Map Container. When you click an aliased <topichead>, the Site Tree remains open, and the CMS displays the parent aliased DITA asset of the <topichead> element in the main pane.

Additional Information
If you have questions or encounter further issues, contact Ingeniux Support.
There are no comments yet.