Unrelated DITAMAP being published
Posted: Tue Apr 07, 2026 5:12 pm
Hi all,
We are running into an issue with one of our DITAMAPs where an extra map is being published along with the main map. This is not a submap in the main map nor is it linked anywhere in the DITAMAP, and we do not know why it is being published.
We confirmed with our documentation portal that they are receiving both maps in the zip archive. Publishing this map from our CCMS does not cause the second map to be published, so it seems to be an Oxygen issue.
I have tried using a process of exclusion to narrow down the offending map/topic, but I was not able to identify a single source which leads me to believe there are multiple files causing it.
Our workaround for now is we added the extra map as resource-only to the main map. This prevents it from being published as a second DITAMAP, but does not reveal the cause.
We would appreciate any help identifying the issue here.
We are running into an issue with one of our DITAMAPs where an extra map is being published along with the main map. This is not a submap in the main map nor is it linked anywhere in the DITAMAP, and we do not know why it is being published.
We confirmed with our documentation portal that they are receiving both maps in the zip archive. Publishing this map from our CCMS does not cause the second map to be published, so it seems to be an Oxygen issue.
I have tried using a process of exclusion to narrow down the offending map/topic, but I was not able to identify a single source which leads me to believe there are multiple files causing it.
Our workaround for now is we added the extra map as resource-only to the main map. This prevents it from being published as a second DITAMAP, but does not reveal the cause.
We would appreciate any help identifying the issue here.