Pages: 1
Print
Author Topic: Purposely Excluded Conrefs Still Listed in Output Log as missing  (Read 4769 times)
Penthesilea
Member

Posts: 4


« on: June 24, 2009, 08:30:09 AM »

Below is an example of the errors listed in the output log.  The conref below has been exclude using a conditional product tag; however, it is still listed as missing. 

We have just begun implementation; however, I'm concerned these errors will pollute the output log to the point where it is unusable or potentially cause other problems.  Is there something in our implementation causing this or should we simply ignore.  XMetaL version 5.01
*****************************************************
<log_line>[xslt] [DOTX010E][ERROR]: Unable to find target for            conref="../Conrefs/ct_2D_platform.xml#ditacomponent_9C444A9F1B664CABAC90EE0D6693AF52/section_B447582BEFB643228D159AF8D521672A".
            Check to make sure that the target element is available, and that it is a 'xxxx'
            element.     Note:'../Conrefs/ct_2D_platform.xml#ditacomponent_9C444A9F1B664CABAC90EE0D6693AF52/section_B447582BEFB643228D159AF8D521672A'
            might be changed to use default dita topic file extension name '.dita' or '.xml'. Check
            to make sure the target of conref is correct.</log_line>
Logged
severin.foreman
Member

Posts: 47



« Reply #1 on: June 24, 2009, 08:55:09 AM »

We had this issue. It occurs when the conditional processing attribute value is set on the conref target instead of on the element that contains the conref attribute. The reason is that, during processing, the open toolkit filters content based on your conditional text settings before it resolves conrefs. To resolve the issue, set the product attribute value on the same element that has the conref.

=== The wrong way to do it ===
Topic A contains a paragraph that conrefs from Topic B.
<topic id="topicA">
  <title>Topic A</title>
  <body>
    <p conref="topicB.xml#topicA.xml/p"></p>
  </body>
</topic>

The paragraph in Topic B has the product attirbute set and
a DITAVAL file excludes the content from the build.
<topic id="topicB">
  <title>Topic B</title>
  <body>
    <p id="p" product="01">Some text.</p>
  </body>
</topic>

When the OT processes these files, the paragraph in topic B is removed before the conref is resolved. Thus, the conref is broken. The output will probably appear the way you want, but it makes your error logs much less useful, as you noted.

=== The right way to do it ===
Topic A contains a paragraph that conrefs from Topic B, but this time the paragraph in topic A is
removed from the topic before conrefs are resolved.
<topic id="topicA">
  <title>Topic A</title>
  <body>
    <p product="01" conref="topicB.xml#topicA.xml/p"></p>
  </body>
</topic>

<topic id="topicB">
  <title>Topic B</title>
  <body>
    <p id="p">Some text.</p>
  </body>
</topic>
Logged
Penthesilea
Member

Posts: 4


« Reply #2 on: June 24, 2009, 09:00:19 AM »

Thanks, Severin!  You rock.  This is exactly what I was looking for.

~ Brittany
Logged
Pages: 1
Print
Jump to: