DITA CMS Core 4.5 Release Notes

BuildRelease Date
4.5.116 June 14, 2018
4.5.98 April 19, 2018
4.5.52 February 22, 2018
4.5.35 December 21, 2017

Build 4.5.116 - June 14, 2018

Important notes

The following documents are available on the IXIASOFT web site: http://archive.ixiasoft.com/en/products/dita-cms/documentation/ 

  • To upgrade Core components from version 4.4 to 4.5: please follow the instructions provided in the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • To update version 4.5 Core components to the current build: please follow the instructions provided in Updating an Existing DITA CMS Core v4.5 Deployment Guide (Update Guide).

 

Bug fixes

  • DEV-5533 When cloning a keydef in DITA Map view and selecting the option "Replace original component", the key value was incorrectly changed to match the new topic ID. This issue has been fixed and the keydef retains the original key value.
  • DEV-5315 When using the Search and Replace feature for documents that had been localized, the Error Log view displayed an "Unhandled event loop execution" error. This issue has been fixed.
  • DEV-5168 In DRM deployments, when opening a map with the oXygen DITA Map Editor, all topics and images used in the map were saved to the user's workspace. This issue has been fixed.
  • DEV-4761 DITA CMS experienced performance issues when working with subject scheme maps in DITA Map view. These issues have been fixed.

  •  

    DEV-3706 In deployments using DRM, the Search and Replace feature would not find any matches when executed from the DITA Map view. This issue has been fixed.

* Indicates that configuration changes need to be applied to benefit from the new features or fixes.

System Requirements

 

Table 1. Server-side requirements
ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
    • If you are using ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th, TEXTML Server 4.3.7.4299 and up is recommended.
  • Operating system:
    • Windows® 2008R2 (64-bits only) and up is recommended.
    • Linux® Red Hat®/CentOS version 5 or 6 (both 64-bits only)
      Note: Red Hat®/CentOS version 7 is not supported.
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.7.4299 and up
Output Generator
  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up; 64-bit
    Note: When you run the integrator on the DITA-OT (for example, run ant -f integration.xml in the command prompt) and you are using Java 1.8, it may give you different results because the plugins are not processed in the same order. Since this may cause a change in the behavior of the plugins, it is recommended that you validate the results before going into production.
  • Rendering software (such as RenderX, Antenna House, or Apache FOP)
Scheduler
  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up, 64-bit

 

Table 2. Client-side requirements
ComponentRequirement
DITA CMS Eclipse Client
  • oXygen® XML 18.x and 19.x
  • XMetaL® XMAX™ 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700], 32-bit or 64-bit
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up (recommended), or Java 1.8.60 and up (limited support), 32-bit or 64-bit
    Note: Java 1.8 support for the DITA CMS Eclipse Client is available, but not recommended and should only be used if absolutely necessary. To use Java 1.8.60 or up, you must install an extra plugin or dropin to patch Eclipse to support Java 1.8. For more information, see the guide: Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • Versions of OS supported:
    • Windows® 7 64-bit version minimum is recommended, but the following are supported: Windows 7 32-bit, Windows 8 64-bit, Windows 8.1 64-bit, Windows 10 64-bit, Windows Server 2008 R2 64-bit, Windows Server 2012 64-bit, and Windows Server 2012 R2 64-bit (RDP or Citrix)
    • Any Linux® platform supported by Eclipse SDK 4.3 (32-bit or 64-bit version)
Important: The DITA CMS Eclipse Client requires good communication with the server components. The latency needs to be better than 50 ms.

 

 

Build 4.5.98 - April 19, 2018

Important notes

The following documents are available on the IXIASOFT web site: http://archive.ixiasoft.com/en/products/dita-cms/documentation/ 

  • To upgrade Core components from version 4.4 to 4.5: please follow the instructions provided in the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • To update version 4.5 Core components to the current build: please follow the instructions provided in Updating an Existing DITA CMS Core v4.5 Deployment Guide (Update Guide).

 

Bug fixes

  • DITA CMS Core
    • [DEV-2102] In DITA Map view, users were able to move the first topic above the title element which broke the map. This issue has been fixed and the up arrow is now disabled when selecting the first topic.
    • [DEV-4132, DEV-4761] DITA CMS experienced performance issues when working with subject scheme maps in DITA Map view. These issues have been fixed.
    • [DEV-4704] When performing a Localize operation in sequential localization, localized content was incorrectly set back to English after edits to other content within the English topic. This issue has been fixed.
    • [DEV-4865] When clicking the Refresh button in DITA Map view or performing an action that caused a refresh of the open map, all of the content above the selected map element was highlighted. This issue has been fixed.
    • [DEV-4867] When a submap was locked from the DITA Map view, the content of the submap was not refreshed with the content from the Content Store. This issue has been fixed.
    • [DEV-5127] An issue occurred when an image was created in a Content Store that was configured with a default language other than English. For example, . If a user created an image without selecting a language from the Language list, the image was created without a language code, and as a result, it could not be found in search results. This issue has been fixed. If you have encountered this issue, please contact the IXIASOFT support team for further assistance with locating and fixing these images.
  • Dynamic Release Management
    • [DEV-3451] When performing a Localize operation in DRM, localized content was incorrectly set back to Localization:tb translated without any edits being made to the English topic. This issue has been fixed.
    • [DEV-4734] DITA CMS experienced performance issues for DRM objects with a large number of dependencies when performing a view dependencies or a delete operation. Performance improvements have been implemented.
  • Output Generator
    • None.
  • Scheduler
    • None.
  • Documentation
    • None.

* Indicates that configuration changes need to be applied to benefit from the new features or fixes.

System Requirements

 

Table 1. Server-side requirements
ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
    • If you are using ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th, TEXTML Server 4.3.7.4299 and up is recommended.
  • Operating system:
    • Windows® 2008R2 (64-bits only) and up is recommended.
    • Linux® Red Hat®/CentOS version 5 or 6 (both 64-bits only)
      Note: Red Hat®/CentOS version 7 is not supported.
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.7.4299 and up
Output Generator
  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up; 64-bit
    Note: When you run the integrator on the DITA-OT (for example, run ant -f integration.xml in the command prompt) and you are using Java 1.8, it may give you different results because the plugins are not processed in the same order. Since this may cause a change in the behavior of the plugins, it is recommended that you validate the results before going into production.
  • Rendering software (such as RenderX, Antenna House, or Apache FOP)
Scheduler
  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up, 64-bit

 

Table 2. Client-side requirements
ComponentRequirement
DITA CMS Eclipse Client
  • oXygen® XML 18.x and 19.x
  • XMetaL® XMAX™ 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700], 32-bit or 64-bit
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up (recommended), or Java 1.8.60 and up (limited support), 32-bit or 64-bit
    Note: Java 1.8 support for the DITA CMS Eclipse Client is available, but not recommended and should only be used if absolutely necessary. To use Java 1.8.60 or up, you must install an extra plugin or dropin to patch Eclipse to support Java 1.8. For more information, see the guide: Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • Versions of OS supported:
    • Windows® 7 64-bit version minimum is recommended, but the following are supported: Windows 7 32-bit, Windows 8 64-bit, Windows 8.1 64-bit, Windows 10 64-bit, Windows Server 2008 R2 64-bit, Windows Server 2012 64-bit, and Windows Server 2012 R2 64-bit (RDP or Citrix)
    • Any Linux® platform supported by Eclipse SDK 4.3 (32-bit or 64-bit version)
Important: The DITA CMS Eclipse Client requires good communication with the server components. The latency needs to be better than 50 ms.

Build 4.5.52 - February 22, 2018

To view the instructions for updating to a new build, see "Updating an Existing DITA CMS Core v4.5 Deployment" on the IXIASOFT web site: http://archive.ixiasoft.com/en/products/dita-cms/documentation/ 

Important notes

To update existing components: please follow the instructions provided in Updating an Existing DITA CMS Core v4.5 Deployment Guide (Update Guide).

 

Bug fixes

  • DITA CMS Core
    • [DEV-4437] After moving topics in the DITA Map view using the left and right arrow buttons and then releasing the map, the topics appeared in their original location. This issue has been fixed.
    • [DEV-4603] When importing an image that was not fully supported, such as a Visio drawing, a message appeared saying that the image preview would not display but that the image would appear in outputs. The message now says: “The image file format of this file is not recognized by the CMS. If it is imported, the image will be stored in the CMS, but it will be not displayed in the Preview view or as a thumbnail. Furthermore, the rendering of this image in an output depends on the capabilities of the selected output type.”
    • [DEV-4645] When localizing from a map at Published:done using concurrent localization, some topicref elements were broken. This issue has been fixed.
    • [DEV-4695, DEV-4796] When selecting a ditaval in the Generate Output dialog box, the DITA CMS Eclipse Client became unresponsive and a Java Heap error was displayed. This issue has been fixed.
  • Dynamic Release Management
    • [DEV-3299] When trying to refactor a topic in DRM, an error message appeared stating that the object could not be moved because the library was closed. Users were then unable to view the values in the Information View for the topic. This issue has been fixed.
    • [DEV-3866] Users were unable to refactor topics to a library if the topic contained internal cross-references. This issue has been fixed.
    • [DEV-4113] The cloning of a version from one product or library to another is no longer permitted, the version can only be cloned within the same product or library.
  • Output Generator
    • None.
  • Scheduler
    • None.
  • Documentation
    • None.

* Indicates that configuration changes need to be applied to benefit from the new features or fixes.

System Requirements

 

Table 1. Server-side requirements
ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
    • If you are using ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th, TEXTML Server 4.3.7.4299 and up is recommended.
  • Operating system:
    • Windows® 2008R2 (64-bits only) and up is recommended.
    • Linux® Red Hat®/CentOS version 5 or 6 (both 64-bits only)
      Note: Red Hat®/CentOS version 7 is not supported.
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.7.4299 and up
Output Generator
  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up; 64-bit
    Note: When you run the integrator on the DITA-OT (for example, run ant -f integration.xml in the command prompt) and you are using Java 1.8, it may give you different results because the plugins are not processed in the same order. Since this may cause a change in the behavior of the plugins, it is recommended that you validate the results before going into production.
  • Rendering software (such as RenderX, Antenna House, or Apache FOP)
Scheduler
  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up, 64-bit

 

Table 2. Client-side requirements
ComponentRequirement
DITA CMS Eclipse Client
  • oXygen® XML 18.x and 19.x
  • XMetaL® XMAX™ 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700], 32-bit or 64-bit
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up (recommended), or Java 1.8.60 and up (limited support), 32-bit or 64-bit
    Note: Java 1.8 support for the DITA CMS Eclipse Client is available, but not recommended and should only be used if absolutely necessary. To use Java 1.8.60 or up, you must install an extra plugin or dropin to patch Eclipse to support Java 1.8. For more information, see the guide: Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • Versions of OS supported:
    • Windows® 7 64-bit version minimum is recommended, but the following are supported: Windows 7 32-bit, Windows 8 64-bit, Windows 8.1 64-bit, Windows 10 64-bit, Windows Server 2008 R2 64-bit, Windows Server 2012 64-bit, and Windows Server 2012 R2 64-bit (RDP or Citrix)
    • Any Linux® platform supported by Eclipse SDK 4.3 (32-bit or 64-bit version)
Important: The DITA CMS Eclipse Client requires good communication with the server components. The latency needs to be better than 50 ms.

 

Build 4.5.35 - December 21, 2017

To view the instructions for upgrading your existing Core 4.4 deployment to the new release, see "Upgrading the DITA CMS Core from 4.4 to 4.5" on the IXIASOFT DITA CMS Core web site: http://archive.ixiasoft.com/en/products/dita-cms/documentation/ 

 

Important notes

Some mandatory changes to the deployment must be made in this release.

  • Upgrade existing Core components: please follow the instructions provided in the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.

 

Bug fixes

  • DITA CMS Core
    • [DEV-2125, DEV-3523] Using the arrow keys to move topics up and down in DITA Map view caused topics to not move or to move to an incorrect location in the map. This issue has been fixed.
    • [DEV-2784] Inline elements such as uicontrol were auto-translated. This caused issues with translation memory since the parent element contained English text and the inline element contained translated text. This issue has been fixed and inline elements are no longer auto-translated if the parent element is not auto-translated.
    • [DEV-3201] When comparing a map to a snapshot, redline compare failed to produce a PDF output with the DITA-OT log reporting an error about the status "tobedetermined". This issue has been fixed.
    • [DEV-3277] Searching for orphaned documents on large content stores caused TEXTML performance issues for all users. This issue has been fixed.
    • [DEV-3526] Changing a topicref to a chapter and then back to a topicref corrupted the map open in DITA Map view. This issue has been fixed.
    • [DEV-3705] When creating a new ditaval and selecting the Use a Subject Scheme drop-down list, existing subject schemes did not appear in the list. This issue has been fixed.
    • [DEV-3737, DEV-4251] When attempting to create a Collaborative Review on a map that contained an out-of-scope cross-reference, an error would occur and the generation of the Collaborative Review would fail. This issue has been fixed. Now, when out-of-scope cross-references are present, a dialog box opens to offer the choice of proceeding with the creation of the Collaborative Review or canceling the operation. This fix has also been implemented for creating snapshots. When the Collaborative Review is opened in DITA CMS Web, an out-of-scope cross-reference appears as unclickable text.
    • [DEV-3891] When performing the Localize operation, DITA CMS was doing an incorrect comparison between the revision of the source topic in the Authoring workflow and the revision of the localized topic to determine if a change had been made. This issue has been fixed and DITA CMS now compares the source topic revision to the localized topic authoring revision.
    • [DEV-3941] DITA CMS displayed an error when importing a localization kit if the only change was letter case. The error indicated that the source files and the translated files were the same. This issue is now fixed for all localization methods, including concurrent localization.
    • [DEV-4039] For sequential localization, topics that had already been translated and had not been edited in English were being set to Localization:tb translated instead of the status defined in the translation.autotranslation.fulltranslation.status field in the localizationManagers.xml file. This issue has been fixed.
    • [DEV-4128, DEV-4129, DEV-4208] Multiple display issues with the Ditaval view were reported. These issues have been fixed so user-specified settings such as column widths and expanded or collapsed state of the folders in the view are retained after a DITAVAL is released or the DITA CMS is restarted.
  • Dynamic Release Management
    • [DEV-3172] In DRM with the auto-translate feature disabled, creating a new instance of a topic and then localizing it auto-translated the topic from the version it was created from. This issue has been fixed and the new instance is no longer auto-translated if the feature is disabled.
    • [DEV-4372] The Select Versions dialog box offered invalid choices when performing an Add to operation. This issue has been fixed.
  • Output Generator
    • [DEV-3737] When attempting to create a Collaborative Review on a map that contained an out-of-scope cross-reference, an error would occur and the generation of the Collaborative Review would fail. This issue has been fixed. Now, when out-of-scope cross-references are present, a dialog box opens to offer the choice of proceeding with the creation of the Collaborative Review or canceling the operation. This fix has also been implemented for creating snapshots. When the Collaborative Review is opened in DITA CMS Web, an out-of-scope cross-reference appears as unclickable text.
    • [DEV-3743] When creating a Collaborative Review in DITA CMS Eclipse Client, the review object was created even if the Output Generator transformation scenario failed. When trying to open the review in the DITA CMS Web, users would see a “404 file not found” error. This issue has been fixed and the review object is only created when the output is generated successfully.
  • Scheduler
    • [DEV-3956]* There was a syntax error in the Scheduler daily_reminder.xsl file. This issue has been fixed and may require a change in your Content Store. See the Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • Documentation
    • [DEV-3738] The topic "Restrict use of output types by role" contained an out-of-date example of configuring the output types. This issue has been fixed by updating the topic with the currently recommended configuration.

* Indicates that configuration changes need to be applied to benefit from the new features or fixes.

System Requirements

 

Table 1. Server-side requirements
ComponentRequirement
TEXTML Server
  • IXIASOFT TEXTML Server 4.3.6.4188 and up
    • If you are using ICU word parsing and localizing in zh-cn, zh-tw, ja-jp, or th-th, TEXTML Server 4.3.7.4299 and up is recommended.
  • Operating system:
    • Windows® 2008R2 (64-bits only) and up is recommended.
    • Linux® Red Hat®/CentOS version 5 or 6 (both 64-bits only)
      Note: Red Hat®/CentOS version 7 is not supported.
DITA CMS Admin plugin
  • TEXTML Admin plugin 4.3.7.4299 and up
Output Generator
  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up; 64-bit
    Note: When you run the integrator on the DITA-OT (for example, run ant -f integration.xml in the command prompt) and you are using Java 1.8, it may give you different results because the plugins are not processed in the same order. Since this may cause a change in the behavior of the plugins, it is recommended that you validate the results before going into production.
  • Rendering software (such as RenderX, Antenna House, or Apache FOP)
Scheduler
  • Java™ 1.7.0_51 or 1.7.0-80 and up, or Java 1.8.60 and up, 64-bit

 

Table 2. Client-side requirements
ComponentRequirement
DITA CMS Eclipse Client
  • oXygen® XML 18.x and 19.x
  • XMetaL® XMAX™ 8.0.1.61
  • Eclipse SDK 4.3.2 [Build id: 4.3.2.M20140221-1700], 32-bit or 64-bit
  • Java™ JRE 1.7.0_51 or 1.7.0-80 and up (recommended), or Java 1.8.60 and up (limited support), 32-bit or 64-bit
    Note: Java 1.8 support for the DITA CMS Eclipse Client is available, but not recommended and should only be used if absolutely necessary. To use Java 1.8.60 or up, you must install an extra plugin or dropin to patch Eclipse to support Java 1.8. For more information, see the guide: Upgrading the DITA CMS Core from 4.4 to 4.5 Guide.
  • Versions of OS supported:
    • Windows® 7 64-bit version minimum is recommended, but the following are supported: Windows 7 32-bit, Windows 8 64-bit, Windows 8.1 64-bit, Windows 10 64-bit, Windows Server 2008 R2 64-bit, Windows Server 2012 64-bit, and Windows Server 2012 R2 64-bit (RDP or Citrix)
    • Any Linux® platform supported by Eclipse SDK 4.3 (32-bit or 64-bit version)
Important: The DITA CMS Eclipse Client requires good communication with the server components. The latency needs to be better than 50 ms.