Documentation Center

Fixed issues in Web/App/Db server

The following Web/App/Db server issues are fixed in Content Manager 14.0.0 compared to 13.0.0.

  • When a custom plugin operation carried out from an inbox called an API, it produced an "object not initialized" error, even if the action completed successfully. That issue has been fixed. [SRQ-11233|CRQ-14852]
  • During publish, when a custom plugin adds extra report items, the publish failed on an Unable to cast object error. That issue has been fixed. [CRQ-14727]
  • Content Manager no longer crashes when an invalid character is introduced in the Baseline name, from a publication title for example. We now return an error instead. [SCTCM-729]
  • The publish plugin IshRemoveNotLockedNavTitles no longer removes navtitles for non-DITA objects. [SCTCM-714|SRQ-10570]
  • When Translation Organizer is integrated with WorldServer using REST APIs, a call to retrieve a client could cause errors such as Sequence contains no matching element. That issue has been fixed. [SCTCM-640|SRQ-10063|CRQ-13761]
  • A retry on a specific WorldServer web services call (CreateProjectGroup) caused Content Manager to create a duplicate of the translation job project. The retry has been removed. The fix applies to both SOAP and REST APIs. [SCTCM-709|SRQ-10626|CRQ-13792|CRQ-13761]
  • The conversion during publish to Dynamic Delivery no longer processes external <xref> elements containing mailto or ftp addresses as broken links, and therefore no longer removes the links from the published result. [SCTCM-696|SRQ-10546|CRQ-13550|CRQ-13613]
  • The IshSaveFilesToRunLegacyScripts plugin now provides the correct file paths for compare folders in a legacy report. [SCTCM-609|SRQ-9975]
  • Using a taxonomy field on only a part of the topics or maps in a publication no longer returns the error Trisoft.InfoShare.BorderControl.InvalidObjectException: The field [FIELDNAME] does not exist when the publication is published or when the Baseline fields are displayed. [SRQ-10737|CRQ-13835]
  • A non-responding URL error is now correctly captured when resolving field values: we now display an appropriate error message instead of the former system failure exception. [SCTCM-731]
  • During a pretranslation purge, the XML attribute values are now correctly processed when they contain entity references: the references are no longer escaped. [SCTCM-713]
  • The ISHRUNDITAOT plugin never allowed draft comments to be published, whether or not the Include draft-comments option was enabled. The plugin now takes account of the option's value. [SRQ-9571|CRQ-14125]
  • Email notification after a status change is no longer failing and returning the An unexpected system failure occurred. Object variable or With block variable not set.