DITA Upload Issues
Condition
After you click the Upload button in the Zip Unpack Options dialog, the CMS checks the uploaded DITA assets for errors. If errors exist, the package displays in the drop zone with a red exclamation mark.
Cause
Uploaded DITA content may contain syntax issues, broken references, or missing dependencies. Ingeniux CMS identifies these issues upon upload, so you can correct them.
Access Error Info
Common Errors
Common upload errors include:
- Invalid syntax error
- The 'conbody' start tag on line 8 position 4 does not match the end tag
of 'concept'. Line 9, position 3
If this error or a similar one occurs, this indicates the DITA content is invalid due to a syntax error. This particular error indicates that the
<conbody>
element is missing an end tag. This error can cause the Missing asset error to occur.Users can resolve this particular validation error by adding the missing
</conbody>
end tag to the appropriate place in the DITA file. - Missing asset error
- "Error occurred converting paths to asset ids: Cannot convert path to
asset id for dita content [a/ID], cannot find asset with path
[path-to-referenced-file-in-zip]
If this error occurs, then a referencing element within the collection points to an invalid path or file, where one of the following issues might apply:
- the path to the referenced file is incorrect.
- the referenced file is missing from the package.
- the referenced file contains a fatal validation error, preventing the file from being referenced by other elements.
Depending on the cause of the issue, users can resolve this particular error by restoring the missing file and ensuring the referencing element points to the correct path. If an overarching validation error is present, then users need to resolve the validation error to resolve the missing asset error.
Remedy
Solutions:
- Resolve the error directly in file uploaded to the CMS.Tip
In the Error column of the dialog, click the asset ID (e.g., a/24729) where the error occurred.
This opens the DITA asset in the Overview tab, where you can open the asset in an editor to fix the issue.
- If the list of errors is extensive, you might consider backing out of the upload by deleting the package from the Asset Tree, fixing the errors in an external editor, then uploading the package to the Asset Tree again.