Page 1 of 1

Filtering of conref push sources

Posted: Tue Dec 23, 2025 6:21 pm
by Tygopit
Hi,
I'm stuck!
I have a bookmap containing topics where certain content is replaced using the conref push mechanism.
I need to use different push resources based on a product attribute, so I created two resource-only topics and included them in my map.
I applied profiling attributes to the topics containing the conref push content, and everything was working fine until this morning.
Now, every transformation generates a warning:
"Two elements both use conref push to replace the target ..."
Additionally, filtering is no longer working as expected.
What could have caused this issue?
Here’s the relevant structure of my map:

Code: Select all

<bookmap>
    ...
    <chapter navtitle="PushSourcesA" processing-role="resource-only">
        <topicref href="reuse/PushSource-SMV-A.dita" product="VA" processing-role="resource-only"/>
    </chapter>
    <chapter navtitle="PushSourcesB" processing-role="resource-only">
        <topicref href="reuse/PushSource-SMV-B.dita" product="VB" processing-role="resource-only"/>
    </chapter>
    ...
    <!-- Topics with push targets -->
    ...
</bookmap>
DITAVAL for Product B:

Code: Select all

<val>
    <prop action="exclude" att="product"/>
    <prop action="include" att="product" val="VB"/>
</val>
DITAVAL for Product A:

Code: Select all

<val>
    <prop action="exclude" att="product"/>
    <prop action="include" att="product" val="VA"/>
</val>
What happened?
What don't I know?

With Christmas greetings
Piotr

Re: Filtering of conref push sources

Posted: Wed Dec 24, 2025 9:49 am
by Radu
Hi Piotr,

As Oxygen does not auto-update, the changed publishing behavior in general means a change in the DITA contents of the project generated it.
For example one of those topics which pushes may be indirectly referenced in other topics or maps? And in those places it does not have the profiling attributes set on the reference? If that does not help maybe you can create a very small DITA project exhibiting the problem and send it over (support@oxygenxml.com).

Merry Christmas from the Oxygen team!

Regards,
Radu