Hi DITA & Oxygen Users,

Currently I want to switch from Oxygen 23 to 25.0 including an extracted build-in DITA-OT3.x with custom pdf2 plugin but In the updated environment we have the following effect:

In almost all DITAVAL contexts (we have a lot) the variable texts are not rendered into the DITA Map anymore without error messages. Just a few DITAVAL contexts produce output as before.

In published content topics/chapters everything is fine -> conkeyrefs are resolved. Also Oxygen Author WYSIWYG resolves all conkeyrefs as expected in topics and in the map.

In the pre-processing output (…_MERGED.xml) the specific map elements do not contain the variable text but conref attributes with wrong transformed links:
The conrefs contain “path/topic.dita#ElementID” instead of “path/ditatopic.dita#topicID/ElementID”

In correct output contexts there are no conref attrubtes rendered into output, just the elements with resolved text.

 

I guess, there could be many different reasons for this. I tried a lot and couldn’t reproduced the problem in a simple test project. I also did´nt manage to simplify our project to a working state.

Maybe someone experienced a similar effect (conkeyrefs in topic content resolved but not in map title/data elements) and can provide hints for a possible cause and or solution.

What I can say so far:
- It has nothing todo with the custom pdf plugin: same problem with build-in pdf and html transformation scenarios.
- We are using only standard pdf parameter settings.
- It has nothing todo with filtering directly because I have deleted all filter atts in the conkeyref chain in scope of the problem. Also our props attribute specialization does not affect the problem.
- We do not use:

-  - scoped keys and ditavalref in maps

-  - push-replace

-  Same problem with and without DITA project files.

- Problem is not caused by DITA topic content structures (I have copied content from working to non-working context.

I'm curious if someone has already seen something like this.

Best Regards

Sascha