-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ditamap with Existing Topicmeta Child Elements Without Critdates Broken on Update #23
Comments
Hi, Firstly, what version of Oxygen are you using? This may help us determine whether the issue is related to the specific version of Oxygen you are using. Additionally, could you please clarify where the map is being opened when you save it? Is it in the DITA Maps Manager or in the main editor? Best regards, |
Hi Cosmin, Thank you for your reply. I am using Oxygen XML Editor 25.0, build 2022121306. I've encountered this issue only when editing the map from the DITA Maps Manager. When I edit the map in the main editor, the plugin does not update the map with the Please see the recording I made showing this issue: dita-prolog-updater-invalid-ditamap-on-update.mp4I hope this helps! Daniel |
Hi Daniel, I can reproduce the problem by having similar settings in the "Plugins / DITA Prolog Updater" preferences page. |
Hi @raducoravu, thanks for the update! I'll stay tuned to hear more updates about this. 😄 For what it's worth, our team is very interesting in using this plugin and think it could be a great addition to our content. However, with the possibility that it can create an invalid DITA Map, we're hesitate to start using it. Thanks again! |
@reifsnid sure, we'll update this thread when we manage to fix this in a future release. |
Given the following DITA Prolog Updater options:
Any ditamap that has existing topicmeta child elements except for
<critdates>
becomes broken when the DITA Prolog Updater adds the<critdates>
element. This is because the DITA schema for ditamaps is restrictive about the order of topicmeta child elements, and the add-on places the<critdates>
element after the existing topicmeta child elements.For example, a ditamap with the following structure:
Would become broken when the DITA Prolog Updater automatically adds the critdates element to the topicmeta:
The text was updated successfully, but these errors were encountered: