CMS 10.6 Release Notes


Release Summary

Ingeniux CMS 10.6 introduces new DITA authoring and publishing pipeline integration, In-Context Editing and Page Builder functionality, user-friendly InSite Search interface configurations, database architecture, and other updates.

Release History

  • June 24, 2024 - Build 10.6.342
  • September 28, 2023 - Build 10.6.308 Initial Release

Build 10.6.347 DSS Only Updates

  • DSS increased response times led to site instability and unsreponsiveness. These issues were caused by excessive resource consumption and contention from the DSS repeatedly rebuilding single object core system metadata after each publish and replication event.

    See the CMS 10.6: DSS Performance Issues Caused By Excessive Rebuilds of Core System Metadata known issue article for details.

    Important

    All CMS 10.6 builds require the latest version of the DSS site's Ingeniux RTAPI NuGet package to resolve this issue. The 10.6.347 prerelease package is available via nuget.org.

    See Updating the DSS RTAPI NuGet Package for details to update.

Build 10.6.342 Updates

  • Check In/Check Out asset folder and children selects now set the current version for asset items.
  • Updated Analytics view to support Google Analytics GA4 Properties.
  • Previewing field content units no longer throws an object reference error.
  • Added fix to ensure newly created content IDs do not conflict with IDs imported by Site Migrator.
  • Dragging zipped Site Migrator packages into the Select a Package... field threw Cannot read properties errors in the Site Migrator > Unpack tab. This error no longer occurs, and the UI now indicates when the package upload process completes.
  • Site Migrator error occurred during the Pack and Download process that prevented the packaged content from downloading. This error no longer occurs.
  • Pages created via page creation rules (PCRs) no longer lose their hierarchical context within the Site Tree.
  • Added scrollbar to Options modal in Properties tab within Site to accommodate overflow and scaling.
  • When loading an asset folder in the CMS UI, the CMS now only makes required search calls. The CMS no longer makes additional ones.
  • Added Creation User, Email, Created Date, and Last Modified Date columns to Unused Assets reports.
  • Asset Tree no longer freezes when users select an orphaned asset in it, and CMS now adds log warnings when it detects orphans.
  • Publish logs did not migrate when upgrading the CMS from version 10.3 and 10.5. The publish logs now migrate on upgrade without issues.
  • Save and Check In buttons became inaccessible for non-administrators with external authentication and with backslashes in their username. Non-administrators can now access these buttons without issues.
  • Added a fix around a race condition where unmarking and publishing pages/assets did not update the page child/asset navigations on the DSS. After unmark/publish, the navigations now update successfully.
  • When users selected multiple list entries via CTRL+Click and then scrolled further down the Administration > Schema Designer > Synchronization list, the CMS did not retain all the user's selections. All list entries now remain selected, no matter if users scroll away from them.
  • Taxonomy Manager became inaccessible after removing English from Worldview page language settings. Administrators can now access Taxonomy Manager, regardless of language settings.
  • Taxonomy Tree drag/drop and copy/paste actions now prevent categories with identical names from residing directly under the same parent category.
  • Taxonomy Manager Search now returns results when users query category IDs.
  • In the Taxonomy Manager Security tab, the Select Access Groups dialog only displayed a maximum of 128 user groups. The dialog now displays all available user groups to choose from within the CMS.
  • CMS upgrades failed if content items had large text element values and numerous version history iterations. This upgrade issue no longer occurs.
  • Custom transition actions without views now run successfully when content items advance in workflow. No error occurs.
  • The Preview iframe temporarily displayed as a blank frame while loading a new page. This Preview page flash issue no longer occurs.
  • The Form edit mode now prevents users from deleting all items in component lists. The list always requires at least one item.
  • Adjusted placement of example text for replication target fields to enhance readability.
  • Added IAM Roles Anywhere and IAM Roles Attachment support for the AWS S3 replication target type.
  • Reduced batch size of file sync report packets to optimize large replication processes.
  • When control of multithread switch was enabled for CMS robocopy replication, the configuration did not take effect. Robocopy replication now honors multithread switch when enabled.
  • Changed the FTP Server Address field label to Host Name in General Settings for SSH replication targets.
  • Fixed issue where non-administrators were unable to add to or transition content items in workflow if the content item was checked in.
  • Fixed issue that allowed all available groups to publish when users only selected one group from the publishing target's Security tab.
  • Fixed issue that prevented users from removing groups from the security manager of a publishing target.
  • Added fix ensuring that security group selections within a single publishing target do not propagate to other publishing targets.
  • The asset history feature was not responsive to certain display dimensions. Now, all versions in an asset's history are visible, regardless of display dimensions.
  • When users canceled a publish, its processing would halt but the Publishing Monitor continued to display the status bar associated with the canceled publish. Now, when users cancel a publish, processing halts, and the Publishing Monitor clears the status bar.
  • Fixed issue that prevented the CMS from syncing pages to reflect changes to the component type configuration.
  • After syncing instances of embedded components, the list of synced instances would disappear. Now, the Schema Synchronization area retains this list after the sync has completed.
  • Periods (.) were not preserved in URLs when the Preserve periods in URL setting was turned on in publishing target Structured URL Settings. The CMS now honors the setting.
  • Disabled custom tabs displayed in the CMS UI. Custom tabs are now hidden from view when disabled. This setting resides in Administration > System Options > Custom Tabs > Display.
  • Fixed issue that caused the Save button in the Design tab to become inactive after back-to-back drag operations into Page Builder drop zones.
  • Addressed CSAPI issue that caused a stack overflow exception when using CategoryNode(), RemovePage(), and RemoveContentItem().
  • Updates to default link values in Schema Designer did not change the DefaultValue field in the database because of an inaccurate payload was sent to the server. Now updates to default link values are saved and accurately display when creating new pages.
  • The schema upload process converted multi-select elements to attributes. Schema Designer now preserves these multi-select elements on upload.
  • Fixed issue that prevented the ancestor navigation order on applicable schema elements from taking effect.
  • DSS navigations updated inconsistently when pages were published with a start and end date set for the navigation. This issue no longer occurs.
  • When users created a new page via the Dashboard > Create New action, an error occurred if the associated workflow's initial transition advanced the new page to the user's group that had security permissions to access the PCR they chose. This error no longer occurs.
  • Fixed a label issue for enabling/disabling Local Exports for the CMS/DSS in System Options.
  • IGXSystem is no longer available as a user account in Administration > Users/Groups.
  • Fix/Replace button did not display for broken reference reports in Administration > Find/Replace. The button now displays; users can replace broken references without issue.
  • Fixed issue where component thumbnails were generating at mobile/tablet width if DSS Preview implementations had response design considerations for components.
  • The Last Modified date and Last Modified User values of each schema reflected changes made by the CMS system during the upgrade process and not by users. These values now only reflect user changes after upgrade.
  • Fixed issue where Keymatch .csv import failed to import the Abstract data for entries, which caused filtering in the Keymatch configuration UI to not work.
  • When users check in content items, the Check in pages to be published dialog provides all publishing targets as available options, even though the content item is not marked for every publishing target. The dialog now only lists publishing targets where the content item is marked for publish.
  • Removed the VaryByUserAgent cache from standard DSS stock sites.
  • When extracting .zip content, the CMS threw an error on the fileName parameter referenced by the OnBeforeUpload custom hook. This error no longer occurs.
  • When the Attributes tab is selected, the Fields tab now only provides Attribute as an option in Schema Designer > Create/Edit. To display element options, select the Elements tab.
  • Site Migrator now displays a visual progress bar to indicate the upload status of ongoing unpack operations.
  • When the RavenDB service for a CMS was not running, the CMS would throw a .NET server error and the login page did not display. The login page now displays with an error message, indicating the server connection could not be established.
  • Improved speed of addressing conflicting asset names during the asset upload process.
  • The ID column now displays directly to the left of Name column in the Assignments pane. When the pane is minimized, the Type, ID, Name, and Notes columns display.
  • Images added to content units in Page Builder layouts did not remain after users saved their changes. New images now remain in the layout after save.
  • In Page Builder, after adding a non-reusable content unit to a layout, the unit stopped displaying in the Design > Content list, including when users deleted then recreated the presentation in the container. The content unit now displays in the list after the deletion/creation of the presentation.
  • Site Migrator did not migrate schema attribute data. Now, when unpacking schemas from packages, all schema attributes and their values are included.
  • When users uploaded a Site Migrator package, the Map Schemas and Map Asset Schemas actions remained unavailable. These actions now become available after upload.
  • The Legacy package detected notification message now immediately displays in the Site Migrator UI when users choose a legacy package to unpack.
  • Site Migrator incorrectly identified CMS 10.0–10.3 packages as legacy packages, causing conflicts that interrupted the unpack process. These packages are no longer flagged as legacy ones.
  • After Site Migrator unpacked a package, the content item order in the Site Tree did not match the order in the package. Unpacked items now display in the correct order in the Site Tree.
  • In the Advance Workflow dialog, users can now view the visual workflow diagram without scrolling.
  • Improved file replication target performance.
  • In the Advance Workflow dialog, users can now view the visual workflow diagram without scrolling.
  • In the Advance Workflow dialog, the Assign To field did not have a default list option selected. The field now automatically provides a selected default option.
  • Enhanced performance of URL map build times during publish.
  • Updated the dialog text for the Undo Check Out action on asset folders in the Asset Tree.
  • When publishing asset folders and their descendants, the CMS removed periods (.) and any text following the period from the folder names. The CMS now retains the full folder name after publishing.
  • When installing a new CMS site or upgrading, the externalmodules.json file was not created. This file is now created on new site setup/upgrade. If externalmodules.json already exists, the CMS does not overwrite the existing file on upgrade.
  • When the Restrict "Allow user to advance workflows assigned to others" to members of the current workflow group permission was cleared in System Options for Workflow, the CMS did not adhere to the permission setting. Now, the CMS prevents users not part of the current workflow group from advancing content items when the permission checkbox is cleared.
  • The custom index did not load in RavenDB after users set up and deployed the CustomIndexes.cs file. The custom index now loads.
In-Context Editing (ICE) Updates
  • Fixed issue when saving a page containing a new ICE template would not render all ICE-compatible child elements as editable.
  • Invalid thumbnails had been generated for ICE components. ICE now uses the correct data/view to generate component thumbnails.
  • Fixed issue where empty links were not displaying in ICE when created through the Trays templates.
  • Addressed an issue in ICE mode where grouped elements within components did not function properly due to fullUniqueID including the unique ID of group elements.
  • Corrected issue that prevented Asset Link Set implementations from generating ICE fields.
  • When ICE users made changes to elements under the Group Start element via the Edit in Field icon, ICE did not save the changes. ICE now saves changes to these elements without issue.
  • Eliminated the need to refresh or save an ICE page to display modified links.
  • Users can now save pages when they only add an image to an XHTML editor field in ICE mode.
  • ICE mode did not display changes to content units until users refreshed the ICE UI. Content unit changes now display automatically without refresh.
  • In ICE mode, pasting text into an XHTML element did not trigger the Save action for the element or page. The action now becomes available after pasting text in the element.
  • In ICE mode, the eraser icon has been removed from the list element at this time. Until this functionality is re-implemented, we recommend that users delete individual list child elements in ICE instead.
  • In some ICE implementations, XHTML elements displayed duplicate ICE toolbar buttons after users made changes. These buttons no longer duplicate.
DITA Publishing Pipeline Updates
  • Normalized child maps contained asset IDs in references when conditional processing was applied to the parent map. References now contain correct relative paths.
  • By default, the CMS removes document type declarations from DITA content before publishing normalized DITA with the DITA Open Toolkit. New feature adds option to disable the removal of document type declarations.
  • DITA Preview now loads properly without throwing errors.
  • Fixed an issue where the DITA Properties tab would make two API calls for DITA dependencies.
  • Navigation on links to DITA aliases had displayed as alias IDs instead of alias paths, resulting in broken links. Links to aliased DITA topics now display as alias paths.
  • DITA content using custom DTDs displayed an empty document type label next to the asset name in the Asset Tree and next to the alias name in the Site Tree. These DITA files now fallback to the default DITA label.
  • Addressed issue where the deserialization of a large DITA dependency file caused the DSS application pool to recycle when DITA content contained validation errors.
  • CMS now prevents users without alias group permissions from accessing the DITA Properties > Alias Management tab and from creating/deleting aliases via the Site Tree and Asset Tree.
  • DITA Map Manager did not return map results when advanced filters were applied. Relevant results now display when using advanced filters.
  • Users without alias management permissions can no longer access the Manage Aliases tab in Administration > DITA > DITA Map Manager.
  • Updated Site Migrator unpack behavior for packages containing DITA aliases. If unpacked to a CMS with DITA configured, the alias structures display in the Site Tree. If aliases are unpacked to a CMS without DITA configured, an error occurs, indicating the CMS requires DITA setup before unpacking them.
  • The Site Migrator unpack operation did not update DITA references to point to the new a/IDs of unpacked DITA assets and aliases. This operation now updates DITA references with the correct IDs.
  • Conrefend attribute values now display as CMS asset IDs instead of relative paths.
  • Clearing the Transform Output Formats button in the Configure DITA Publishing dialog disabled its Continue button when normalization was the only selected transformation. Now, the Continue button remains active under these conditions.
  • Updated error message for when the CMS fails to upload a custom DITA-OT plugin. The error now specifies the transtype is invalid/missing in the plugin package.
  • DITA maps can now be published using DITAVALs that haven't yet been marked for publish.
  • Enhanced performance of the DITA Map Manager and the DITA publishing map selection dialog.
  • If users searched for a DITA alias residing under a Site Tree page they did not have permissions to access, CMS search threw an error. Now, for users without permissions to the parent page, search no longer throws an error, and the alias does not display in returned results.
  • In normalized DITA outputs on the DSS, links generated by the DITA-OT no longer go to the asset URL path of the DITA content. Instead, these links now go to the correlating alias URL of the DITA content.

Important

  • As of CMS 10.6, site upgrades on existing CMS instances no longer attempt to create a backup of the pre-upgrade Raven Database (RavenDB). You will be prompted to ensure you create a database backup prior to running an in-place upgrade.
  • Removed the deprecated Google Analytics OAuth out-of-band (OOB) flow. If you have Google Analytics configured for your Publishing Targets, you will need to reconnect these profiles.
  • Deprecated the navigation types "sequential" and "subtree" for navigation elements. The options now display as deprecated and inactive after CMS site upgrades.
  • Customers who have existing In-Context Editing or Page Builder implementations for their sites may need to make adjustments to their DSS implementation code for compatibility within CMS 10.6.
  • TinyMCE no longer supports smart paste in the CMS. As such, the setting has been removed from Administration > System Options > CMS > XHTML Editor.

Key Enhancements

Improvements

  • Administrators can now use Site Migrator to pack and unpack asset-only packages. This feature is also used extensively to support migration of DITA asset content—when the CMS unpacks DITA content, the system maintains asset ID references and updates the DITA assets with new IDs.
  • Added Themes tool in Administration > System Options > CMS > Themes. Administrators can now create and edit custom color themes for users to choose from and to display in their CMS UI.
  • Changed default setting of specific Secure Shell (SSH) key exchange algorithms for SFTP access to assets. These ciphers now disable by default for security purposes. Users can change the SFTP server SSH parameters as needed.
  • Added WYSIWYG edit mode to the Edit tab of HTML assets. Users can now edit HTML asset type content via the visual XHTML (TinyMCE) editor or the text (Ace) editor.
  • Users can now sort by xID in the Component Picker dialog box.
  • Pressing the ENTER key after typing a value for the Search Text field in Find/Replace will execute the search.
  • Added Web.config setting to enable and configure allowed HTTP verbs in the Swagger UI. If not set, the system only allows GET and HEAD.
  • By default, Administration > Publishing Logs now displays the logs for the publishing target currently selected in the Site Tree. Administrators can view logs for other publishing targets via the Select Publishing Target drop-down list.
  • CMS now prevents replication targets from using identical names. Each target now requires a unique name.
  • The Analytics app has been moved to the CMS Administration section and is no longer a custom application. Once configured, the Analytics profile is stored within the database instead of within an external configuration file. This allows for the Analytics configuration to be automatically included in a site export.
  • The Site Tree content item Edit form now displays a UI indicator icon when element fields contain 1) assets not marked for publish to the current publishing target and 2) assets marked for publish that have never been published.
  • Enhanced the Mark/Unmark for Publish dialog UI. Updates include a search field to filter available publishing targets.
  • Users can now use Diff Content to render and compare versions of the same DITA asset via the asset's History tab.
  • You can now edit the URI of an external asset, which will update relevant metadata/asset information as well.
  • Changing the DSS log level no longer requires a recycle of the DSS application pool for the change to be applied.
  • Updated Rest API calls to replication profiles.
  • Added warning log entry for the CreateAssetFolder method with overwrite set to true. If applied, this CSAPI method deletes existing asset folders before creating the new one.
  • Added OWIN class interface for custom tab implementations.
  • Added Finalize Schema button for working with draft mode schemas. This button saves the schema as a new version.
  • Links to assets in XHTML elements on pages that more than a single level deep from the home page xID would render the path to these assets with an additional leading path traversal (e.g. ../../) as part of the path. Now, only links to DITA assets will have the relative path traversal for the purpose of rendering DITA content properly on a DSS site.
  • Links to assets threw errors in workflow notification emails. These links now go to the correct assets without issues.
  • The CMS now provides warnings at export time and during site setup to identify long paths within an export without stopping the setup process. The logs will provide details if the system fails to include paths from the export during site replacement.
  • Updated the Administration > Publishing System UI
  • Updated the Mark/Unmark for Publish dialog UI.
  • Added the Cache404Page appSetting to the stock DSS Web.config, for use in caching the publishing target defined 404 page to improve DSS performance. This setting is disabled by default.
  • Creating a new custom tab now validates the name up front instead during a save.
  • The Find/Replace Broken References tool no longer flags 3xx status codes as broken.

Fixes

  • Diff Against Version views no longer display errant HTML tags when displaying differences in pillbox selectors.
  • Loading loop error occurred for text-based assets with missing binary files on disk. The CMS now displays an error for these assets. The loading loop no longer occurs.
  • Global static and dynamic variables did not update in DSS Preview when they were configured for multiple publishing targets. DSS Preview now renders the variables as expected based on the selected publishing target.
  • The Categorize tab would incorrectly show an arrow indicating a child taxonomy category on nodes that contained no children.
  • When users chose a publishing log after viewing the log of a failed publish, the chosen log never loaded. All publishing logs now load successfully.
  • Restored field attribute validation in the Create/Edit screen of Administration > Presentation Content Units.
  • After CMS upgrade, content items now retain the names of their embedded components in XML and in the Edit tab.
  • Forced exceptions thrown during a publish operation would falsely report that the entire publish operation failed and not write publishing logs despite it having been completed.
  • Uploading and extracting zipped assets with deeply nested filepaths to the Assets Manager no longer throws a stopping error.
  • XML field content units converted to plain text after users saved the units via Administration > Presentation Content Units. These content units now remain as XML field types after saving.
  • Updated the Schema Designer element tooltip for component fields. The tooltip now tells users to enter the component xID that will serve as the default value.
  • The DSS threw an options.xml file lock error after replication to the DSS completed. To resolve error, added app settings to retry SafeXML load attempts on locked files.
  • Added circular reference check to taxonomy categories.
  • CMS upgrade logs now show full filepaths if errors occur when accessing (deleting/restoring) a particular item during upgrade.
  • Administration > Analytics and the Analytics tab threw errors if users attempted to filter Google Analytics data when the Start/End date fields were set to past dates. Users can now filter by date without issue.
  • Inserting bold text into an XHTML element within a list will no longer inserts extra source code attributes for the text.
  • If administrators gave schemas a boost entry before disabling them from indexing, duplicate SearchSource.config entries generated for the schemas. The system now prevents entry duplication on serialization.
  • Asset names are now sanitized on creation to prevent characters that are not compatible with the Windows file system.
  • Handled missing descriptive metadata fields in new asset schemas. The missing fields led to missing custom XMP metadata.
  • Content units with views were required to be marked for publish via the Content Unit View History dialog. Users can now mark/unmark content units with views as needed.
  • In-Context Editing (ICE) fields now show as editable if the field's ancestor list/component is not configured for Wrap in Expanded XML on the schema itself.
  • Double-clicking on an image asset in the Asset File Browser dialog will now bring up the image editor for the asset.
  • Failed upgrades with a rollback action would sometimes fail on subsequent upgrade attempts with an error that LICENSE.txt already exists. Upgrades now complete without error.
  • Utility search can now run partial word queries.
  • Users logged into multiple browsers will not show duplicate active user entries on the Dashboard.
  • Disabling Auto-Save in the CMS now prompts the user if they wish to save changes or not.
  • Users/groups with a large count of assigned content items no longer causes the CMS to freeze when viewing Assignments.
  • Site tab no longer fails to load intermittently when requested from the Assignments list pane.
  • Included XML files in the RTAPI and CSAPI for Intellisense support.
  • Users can now paste a value for the Additional CSS Class field for a Page Builder presentation.
  • Taxonomy associations can now be sorted on the Name column when clicked.
  • If a new CMS site installed with a site export and with replication targets disabled on setup, the installation failed due to a replication target certificate error. The installer now runs successfully without error.
  • Fixed a missing image in the Taxonomy Manager view.
  • Site replacements inaccurately updated assets with binary files. The assets now update to the correct version without issue.
  • Initializing the DSS with CMSPageFactory.GetDefaultSitePath() no longer throws a missing content folder error.
  • Users with the Allowed to assign pages not assigned to them to others permission can now delete assets assigned to the default IGXSystem user after a CMS system upgrade from version 9 to version 10+.
  • Clearing the Unpack zip packages checkbox now makes other settings unavailable in the Zip Unpack Options dialog. The inactive settings only apply when the uploader unpacks zipped assets.
  • Administration > System Options > CMS > Email no longer requires the email address display name value in the User Manager Address field.
  • When users extracted content from uploaded .zip files and resolved naming conflicts by creating new assets instead of updating the existing ones, the Asset Uploader didn't create the assets. Now, if naming conflicts exist in extracted .zip files, the uploader successfully creates the new assets.
  • Removed Expand on Publish and Render on Publish checkboxes from Publishing Management Properties on components and folders. Content issues occurred when the checkboxes were selected.
  • Added table sorting functionality in Administration > Redirects.
  • Users who executed workflow transitions with email actions did not receive notifications, no matter that their group was included the recipient list or that their workflow notifications were enabled. These users now receive notifications.
  • Dragging managed asset folders to unmanaged parent folders caused unmanaged child assets to vanish in the Asset Tree, no matter that the children were still on disk. The children now remain visible.
  • Removed Content Localization Workflow settings from Administration > System Options > CMS > WorldView.
  • Replication target types can be selected for a new target even if all existing replication targets have been expanded in view.
  • Fixed a number of keyboard shortcuts that can be used for certain CMS actions.
  • Corrected several field validation messages when working with various elements in Administration > Schema Designer.
  • Start/End dates on assets are now respected when requested on the DSS site.
  • Pages set to Expand on Publish no longer cause incremental publish errors.
  • Clearing a component list that contains a mix of selected and embedded components no longer throws an error.
  • Site setups using an export that was in a content freeze state now remove the content freeze flag from the export during setup to prevent setup failure situations.
  • Replication status UI updated to be more accurate when viewing them in Administration > Publishing Monitor.
  • Renaming an asset content item will now update the technical metadata of the asset as well.
  • New custom tabs scoped to a page no longer revert to Global on initial configuration.

Known Issues

Any known issues related to this release will be updated here as they are reported. If you encounter issues not in this list, report them to Ingeniux Support.

All CMS 10.6 builds contain the following known issues:

  • DSS Performance Issues Caused By Excessive Rebuilds of Core System Metadata. DSS increased response times led to site instability and unsreponsiveness. These issues were caused by excessive resource consumption and contention from the DSS repeatedly rebuilding single object core system metadata after each publish and replication event.

    Upgrade your DSS site's Ingeniux RTAPI NuGet package to the latest 10.6 version. The 10.6.347 prerelease package is available via nuget.org.

    See the known issue article for details.

  • Unauthorized users can embed components in ICE. In-Context Editing (ICE) permits users to embed/unembed components in content items regardless of their user group permission restrictions.

    See known issue article for details and workaround.

  • Page navigations do not reflect changes to the DITA alias structure. Incremental publishes of DITA content do not rebuild page navigations on the DSS. If DITA alias structures contain new changes since the last incremental publish, the DSS page navigation does not reflect these changes.

    See known issue article for details and workaround.

  • XML tab displays incorrect FileName attribute for the Asset LinkSet element. The XML tab incorrectly renders the FileName attribute value for assets referenced in the Asset LinkSet element. Use the workaround to render the correct value.

    See known issue article for details and workaround.

  • Workflow notification emails contain invalid links. Invalid links reside in workflow notification emails sent from the CMS to users because of new emailer template file changes.

    See known issue article for details.

  • Sorting is unavailable for InSite Search Keymatch entries. Column sorting is unavailable for the keymatch entry table in InSite Search Configuration.

    See known issue article for details.

  • DSS stability issues occur when rendering DITA with complex dependencies. DSS stability issues occur when rendering DITA collections with deep and complex dependency structures. These issues cause frequent application pool recycling events.

    See known issue article for details.

  • Exporting a site with a content freeze may fail because of a non-permissioned user. If an administrator uses a site export under a content freeze, the setup process of the new CMS site may fail if the same user account is not provided as the initial user during the configuration of the Ingeniux CMS Site Setup Wizard.

    See known issue article for details.

  • TinyMCE override for SSL-terminated environments. CMS users who work in an SSL-terminated environment may experience a "mixed-content" warning while editing pages that contain XHTML fields.

    See known issue article for details.

Build 10.6.342 contains the following known issues:

  • Error prevents user group "Security Root Pages" tab from loading. The user group Security Root Pages tab throws an "Invalid grid data: Page data overflow" error when the group has permissions to many content items, asset items, and folders. This error prevents the security root pages list from loading.

    See known issue article for details.

Build 10.6.308 contains the following known issues:

  • Google Analytics 4 (GA4) Data Streams are not supported for publishing target analytics configurations.
  • Content Creation Wizard prevents using the "Drag and Drop" action. The Content Creation Wizard UI prevents users from dragging and dropping page creation rules (PCRs) in the Site Tree.

    See known issue article for details.

  • "Check In" dialog provides unmarked publishing target options. The Check in pages to be published dialog provides all publishing targets as options instead of only providing targets where the content item is marked for publish.

    See known issue article for details.

  • Schema "Last Modified" values are inaccurate after upgrade. The Last Modified date and Last Modified User values of each schema reflect changes made by the CMS 10.6 upgrade process and not by users.

    See known issue article for details.

  • IGXSystem user is included in the Users list. IGXSystem is included as an available user in Administration > Users/Groups; however, this user role is for internal CMS use only and should not display in the Users list.

    See known issue article for details.

  • Canceled publish is not reflected in the Publishing Monitor status. The status bar remains visible for canceled publishes in Publishing Monitor. Users may assume the publish was halted and not canceled.

    See known issue article for details.

  • Non-Administrators with external authentication and with backslashes in their username cannot view "Save" and "Check In" buttons. Non-administrators with non-integrated authentication (e.g., SAML, Active Directory) experience an inactive Save button and missing Check In button in the toolbar when their username contains backslashes.

    See known issue article for details.

  • Missing document type label for DITA files with custom DTDs. No documentation type label displays for DITA files with custom DTDs in the Asset Tree and Site Tree.

    See known issue article for details.

  • Presentation component unit thumbnails generate with mobile device width. For responsive presentation component units, the CMS generates thumbnails with a width meant for mobile devices instead of desktop.

    See known issue article for details.

  • Cannot save content pasted in ICE XHTML fields. In-Context Editing (ICE) prevents users from saving their copy/paste changes in XHTML editor fields.

    See known issue article for details.

  • Check-in from Asset Tree folder does not select the current version of marked assets. Using the Asset Tree Check In context menu action on the parent folder does not select the current version for marked child assets.

    See known issue article for details.

  • Reverted pages requiring synchronization do not display in the Schema Designer "Out-of-Sync" list. After reverting a page to an earlier schema version, Schema Designer does not recognize the page as out-of-sync.

    See known issue article for details.

  • Page field changes do not automatically save when users perform workflow actions. The CMS does not automatically save changes to page field content before the user executes workflow actions on the page.

    See known issue article for details.

Who Should Upgrade

  • Customers running CMS 10.0 through 10.5 should upgrade to CMS 10.6.
  • CMS 9.0 customers should upgrade to CMS 9.0 SR8 prior to upgrading to CMS 10.6.
  • Ingeniux CMS OnDemand customers will be contacted by Ingeniux Support regarding the schedule for their OnDemand UAT and upgrade.

Upgrade Guidelines

To upgrade to Ingeniux CMS 10.6, follow these steps:

  1. Review the Ingeniux CMS System Requirements.
  2. Review the CMS 10 Upgrade Guide.
  3. Contact Ingeniux Support to request a CMS 10.6 product key if you do not have one already.
  4. Configure a test environment with CMS 10.6 using a replica of the CMS 8.0 XML content or CMS 9.0/CMS 10.0+ site export.
  5. Create a new site in the test environment using the CMS and DSS Site Setup wizards. See the Installation Guide for details on how to do this.
  6. Run the Ingeniux CMS Site Instance Wizard in the test environment to upgrade the site content to the latest version of Ingeniux CMS.
  7. Evaluate the site implementation in CMS 10.6 within the test environment.
  8. Perform a full publish and set up a DSS site in the test environment to evaluate the latest DSS features. A DSS site upgraded to 10.6 code base will only render content published from a CMS on 10.6.
  9. Implement the CMS 10.6 upgrade in the production environment with the same process.

Ingeniux Support is available to work with your organization to determine the optimal plan and time frame to upgrade to the Ingeniux CMS 10.6 release.

License Key

Customers who upgrade to Ingeniux CMS 10.6 must obtain a new license key for this release. Please contact Ingeniux Support at 1.877.299.8900 or support@ingeniux.com to request a new product key.

Contact

Contact Ingeniux Support at 1.877.299.8900 or support@ingeniux.com with any questions.