move-meta error with topic reused in two or more chunks

[WWamsley]

Hello,

We are currently using Webhelp v25.1, but I also experience this issue with v26.1. When a topic is referenced as a child in two or more chunks, a [move-meta] File ... was not found is displayed in the logs.

Here is an example of how the topics are structured in the map. Remove the chunk attributes OR either of the shared_topic.dita references, the error is resolved. Doing such is not ideal as it changes the intended structure and reuse case.

Code: Select all

    <chapter chunk="to-content" href="topics/topic_1.dita">
        <topicref href="topics/shared_topic.dita"/>
    </chapter>
    <chapter chunk="to-content" href="topics/topic_2.dita">
        <topicref href="topics/shared_topic.dita"/>
    </chapter>

Interestingly, this error doesn't occur when running the transform from OxygenXML Author. However, when running the same transform from either the DITA command line or our CCMS, the error appears in the log. Despite this error, the outputted files look accurate as intended. Our issue is the CCMS treats this as a hard failure X, misinforming the user that something is wrong.

After diving further into the issue, I discovered that some <bookmeta/> elements trigger the issue. This makes some sense as the error appears related to metadata. Remove the below elements, the issue goes away. However, again, this metadata is important to the document.

Code: Select all

    <bookmeta>
        <!--- The bookmeta elements below trigger the 'not found' error.  -->
        <publisherinformation>
            <published><revisionid>2</revisionid></published>
        </publisherinformation>
        <critdates>
            <revised modified="2025-03-05"/>
        </critdates>
        <permissions view=""/>
        <prodinfo>
            <prodname/>
            <vrmlist>
                <vrm version="1.0.0"/>
            </vrmlist>
        </prodinfo>
    </bookmeta>

This error seems to strictly be from webhelp-responsive. This error does not appear in our other plugins such as the generic html5 of DITA-OT. This is certainly an odd issue and I am unsure how to resolve. I have quite a few large documents that have chunks like this. It would be preferable if I could avoid re-architecting those documents.

Appreciate any help or guidance. Thanks!

sample-files.zip

[julien_lacour]

Hello,

I reproduced the problem and added an issue in our tracking system.
A new post will be done in this thread when a fix will be available.

Regards,
Julien