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

  • September 28, 2023 - Build 10.6.308 Initial Release

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 contentwhen 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, AdministrationPublishing 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 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 Assets 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 noted on this list, please report them to Ingeniux Support.

  • Google Analytics 4 (GA4) Data Streams are currently not supported for Publishing Target Aalytics configurations.

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.