Prevent insertion of `buildId` in HTML generated by OxygenXML

Post here questions and problems related to editing and publishing DITA content.
teresarich
Posts: 2
Joined: Wed May 28, 2025 10:38 am

Prevent insertion of `buildId` in HTML generated by OxygenXML

Post by teresarich »

Hello,
I have some DITA content that I am publishing to HTML Responsive Webhelp via OxygenXML

For each export, OxygenXML appends the date-time to each import, as a buildId:

Code: Select all

<link rel="stylesheet" type="text/css" href="../../../oxygen-webhelp/template/oxygen.css?buildId=2023042410"/>
The date-time is unique for each publishing run, and can make it appear to our Version Control System that the content has changed - though it hasn't actually.

DITA_OT does not specify the buildId when exporting to HTML - so if none of the content has changed, it's not a new version.

Code: Select all

<link rel="stylesheet" type="text/css" href="../../../commonltr.css">
Can the buildId be excluded from HTML imports during the OxygenXML to HTML publishing process?
IanMayo
Posts: 11
Joined: Thu Jun 08, 2023 6:46 pm

Re: Prevent insertion of `buildId` in HTML generated by OxygenXML

Post by IanMayo »

I got this great answer from Radu a couple of years ago, when I faced the same problem:
https://stackoverflow.com/a/76848786/92441
cosmin_andrei
Posts: 146
Joined: Mon Jun 12, 2017 10:50 am

Re: Prevent insertion of `buildId` in HTML generated by OxygenXML

Post by cosmin_andrei »

Hello,
The build ID is generated to ensure that the browser loads any updates to the template or resources that may occur between deployments.
If you no longer want the build ID to be generated, the approach recommended by my colleague is a valid solution.
Regards,
Cosmin
--
Cosmin Andrei
oXygen XML Editor and Author Support
teresarich
Posts: 2
Joined: Wed May 28, 2025 10:38 am

Re: Prevent insertion of `buildId` in HTML generated by OxygenXML

Post by teresarich »

Hello,
The build ID is generated to ensure that the browser loads any updates to the template or resources that may occur between deployments.
If you no longer want the build ID to be generated, the approach recommended by my colleague is a valid solution.
Thanks for your answer. I got it.
Post Reply