CMS 10.1 Release Notes

CMS 10.1 Release Notes | Details on Ingeniux CMS 10.1, build 10.1.105. This release includes more than 400 updates.


Release Summary

Ingeniux CMS Version 10.1 includes more than 400 updates. Learn more about key enhancements and important upgrade information below.

Build Number

December 12, 2018 - Build 10.1.105 - Latest release update to the initial release of CMS 10.1 (build 10.1.69)

10.1.105 Updates

  • To address DSS Preview performance issues related to global export expansion, the following app settings were added to the DSS web.config (boolean, true by default): IGXPreview/ExpandGlobalExportsOnEntryInit and IGXPreview/PrefetchEntireXmlCache.
  • Added null reference handling for errors that could occur for Multi-format Output publishes/Expand on Publish pages that happen to have references to xIDs that are missing their Page Versions from the database. These offending xIDs will be logged in the CSAPI logs.
  • Added a new appSetting, AttributesWithDynamicVariables, in DSS web.config to define custom root-level Schema attributes that are allowed to contain expanded global dynamic variables.
  • Fixed: Modified CSAPI code to prevent a semaphore limit error that can sometimes occur when conducting large batch operations.
  • Fixed: SignalR calls in the CMS UI would not properly close in some instances, which could result in issues with the CMS not responding for 90 seconds.
  • Fixed: Page Creation Rule Content Upgrader during CMS Upgrade may leave some page creation rules with an empty descriptor, which results in a permission alert when attempting to use the PCR as a non-admin.
  • Fixed: Users who did not have publishing permissions received an error when configuring Workflow Transitions that included a Publish action.
  • Fixed: CMS 9 sites that happened to retain legacy ReplicationTaskDetail documents in RavenDB would result in application pool issues after upgrading to CMS 10. The CMS upgrade process will now test and remove these legacy documents if present.
  • Fixed: Cutting and pasting an asset folder into the same parent node would remove the folder.
  • Fixed: CSAPI Session issue would prevent check-in of pages that contained embedded lists of components.
  • Fixed: Links could be created on XHTML elements for Checked-In pages via drag-and-drop from the Site Tree.
  • Fixed: Checking in an asset to one publishing target would not update other publishing targets to reflect the previous version.
  • Fixed: For site implementations who happened to have StartDate and EndDate reserved values defined as Navigation Exports, a bypass in the RTAPI was added so that these export values would still function after upgrade to CMS 10.1+. Note that if these values are set as navigation exports, they will override Page Properties' Start and End Dates (if configured).
  • Fixed: Navigation Exports that happen to retrieve an Asset ID that no longer exists in the CMS will result in a 500 error in Preview.
  • Fixed: The CSAPI IReplicator.Replicate method call would fail when invoked within a write session.
  • Fixed: The enter key now confirms the OK action when using a Page Creation Rule to create a content item.
  • Fixed: Querystrings were not being passed to the To value for Redirect rules.

10.1.89 Updates

  • Fixed an issue where unmanaging an XSLT/XSL stylesheet asset would incorrectly convert the file type to Text rather than XSLT Stylesheet.
  • Fixed a performance issue when loading large results of components in the Component element's Selection window for non-administrative users.

10.1.86 Updates

  • Fixed an issue with Multi-Format Output publishes not respecting the User Agent and Sites definitions for XSLT stylesheets.
  • Fixed an issue with the EditMode variable value not being consistent between In-Context Editing, Preview, and Design tabs.
  • Fixed an issue where the upgrader from CMS 9 would not migrate the Moved value for pages in URL Map history.

10.1.82 Updates

  • Added additional logging during for the CMS Upgrader.
  • Fixed an issue with where the Broken Reference report would return any external asset if the asset path did not start with a protocol value.
  • Addressed a UI issue where the Asset Folder Overview's "Updated On" field was referencing the last modified timestamp of the DB document instead of the timestamp of the asset itself.

10.1.80 Updates

  • Publish Performance improvements for CMS sites that contain a large amount of external assets.
  • Performance enhancements when using the Go To Search to access a page or asset in sites that contained a large amount of objects.
  • Addressed an issue where custom Locale labels were not showing in the Go To Search.
  • Addressed an issue where elements marked as Hidden within a group that was not Hidden would disappear on Check-In by a user who does not have permission to view hidden elements.
  • Added small fixes to logging messages for Category associations and DB Index events in the CSAPI log.
  • Addressed an issue with Site Tree expansion reporting a null reference error because of an incomplete Recycle Folder empty event.

10.1.76 Updates

  • Added the ability to update Name and Description properties for Taxonomy categories via REST API.
  • Addressed an issue with the External Client Workflow Action not receiving the PageID and TransitionID parameters.
  • Addressed an issue where non-admin users would encounter a "WHY ERROR?" message when attempting to copy and paste Categorized pages with the "Copy Categorization Info on Page Copy" option enabled in the CMS.
  • Addressed an issue in the DSS where assets paths that contained a space would result in an extra "a/" in the path when accessing the asset via Asset ID directly.
  • Addressed an issue with the DSS where navigations within an embedded component would not expand.
  • Fixed a UI issue for lists of embedded components only displaying a single component if the list was configured to automatically embed components.

10.1.74 Updates

  • Addressed an issue where Asset redirects will have an extra a/ appended in the URL on DSS if the Asset Path contains spaces.
  • Addressed an issue where navigations within an Embedded Component do not expand on the DSS.
  • Addressed an issue where adding a new Embedded Component List Item via Form View will initially show only one of the component's elements in the list.

10.1.71 Updates

  • Addressed an issue where a Taxonomy category Name or Description could not be updated through a REST API call.
  • Addressed an error that prevented users from dragging and dropping taxonomy categories from child nodes to the root node in the Taxonomy Manager.

Key Changes for Developers

  • DSS RTAPI is referenced and delivered via NuGet instead of with local DLL references. DSS Projects upgraded by the installation wizard will be converted to NuGet references automatically.
  • Upgraded Microsoft .NET Framework to version 4.7.2 which is now a software prerequisite.
  • Added a new element type: XML Field.
  • IsComponent attribute has been added as a default global export.
  • Asset Schema Technical Metadata can be updated via CSAPI using the SetItem method.
  • Fixed an issue where DSS Preview does not load assets when the view contains a hard-coded path to the asset.
  • Default DSS/DSS Preview projects are updated to remove VSToolsPath configuration to support code publishing from Visual Studio.
  • Renamed the Ingeniux.Runtime extension from "ToHashSet" to "IGXToHashSet" in the Runtime API to avoid conflicts in Views due to the .NET Framework 4.7.2 extension of the same signature.
  • Fixed an issue where the blank option was not available when specifying a Navigation Type.
  • Addressed an issue where a Taxonomy category Name or Description could not be updated through a REST API call.
  • Addressed an issue where Asset redirects will have an extra a/ appended in the URL on DSS if the Asset Path contains spaces.

Key Changes for CMS Administrators

  • CMS Content Freeze is automatically initiated during an in-place upgrade.
  • Setting up a new CMS site with the CMS Site Setup wizard using a site export will automatically disable replication profiles for all publishing targets.
  • Paste plugin for the XHTML element is enabled by default for new CMS setups.
  • Last modified date and time for Assets is carried over to their corresponding Asset Schema fields when upgrading from CMS 9 to CMS 10.1.
  • Fixed an issue where editing an existing redirect entry set for all publishing targets would cause the entry to not be set for all publishing targets.
  • Fixed an issue where FTPS Replication Target configuration would not obfuscate the password field in the publishing target settings.
  • Fixed an issue where FTPS replication targets would not respect root path values.
  • Fixed an issue where FTPS replication targets would revert to port 21 when toggling Implicit TLS mode.
  • Fixed an issue where creating new SFTP replication profiles would not save correctly.
  • Fixed an issue where Amazon S3 Replication would not remove files if the target configuration root path contained a leading slash.
  • Fixed an issue when syncing to a component with an image asset specified would remove the asset reference post sync.
  • Fixed an issue where Asset element alt-text value is overwritten on schema sync.
  • Fixed an issue where a processing error occurred when syncing embedded components.
  • Fixed an issue where Find out-of-sync embedded components would result in error "An item with the same key has already been added."
  • Fixed an issue where non-admin users needed the "Allowed to create pages using page types" permission to embed a component.
  • Fixed an issue where categories could not be dragged and drop within the Taxonomy Tree Manager.
  • Fixed an issue during Generation upgrade from CMS 8 to CMS 10 where URL Map files that contained empty Path entries would cause the generation upgrade to fail.
  • Fixed an issue during CMS 9 to CMS 10 upgrades where XHTML elements that referenced Assets whose full path contained spaces would not have the assets migrated to the corresponding Asset IDs after upgrade.
  • Fixed an issue where LinkSet elements that were Filtering for an Ancestor Page would prevent Pasting a New Region Root (WorldView cloning).
  • Fixed an issue that prevented deletion of pages that do not have a Page Version from the Recycle Folder.
  • Addressed an error that prevented users from dragging and dropping taxonomy categories from child nodes to the root node in the Taxonomy Manager.

Key Changes for End Users

  • Added a new element type: XML Field.
  • Option to upload and unpack zip files to Digital Asset System.
  • Categorize tab supports drag and drop of Taxonomy categories.
  • Expand/Collapse all element nodes in Index View.
  • CMS will redirect a user to a provided URL route within the site after a successful authentication.
  • Performance improvement when expanding an Asset folder in the Asset Tree when the folder contains many child objects.
  • Performance improvement when expanding a list of Asset Folders within the "Select an Asset" file browser when the folder contains many child objects.
  • Performance improvement when retrieving the Page Creation Rules tree node dialog when creating a page using a Page Creation Rule.
  • Last modified date and time for Assets is carried over when upgrading from CMS 9 to CMS 10.1.
  • Fixed an issue for CMS sites configured with multiple Analytics endpoints would throw a 401 browser alert on initial load of the Dashboard.
  • Fixed an issue where text within a list of components could not be highlighted/selected within Firefox.
  • Fixed a rare issue where text element content would prevent index and form views from loading.
  • Fixed an issue where descendant count would not return for sites with a high count of nested child objects in the site tree.
  • Fixed an issue with the xID link in workflow notification emails.
  • Fixed an issue where a link with an encoded URL would save as encoded in the XHTML element.
  • Fixed an issue where Diff Against Version in the History tab would not render styling differences in Text elements.
  • Fixed an issue where Asset Schema list elements could not be modified to add new child objects in the list.
  • Fixed an issue where pages in a read-only site tree node could not be passed through a workflow transition.
  • Fixed an issue where an asset folder's child assets would not load in the main pane when the Asset Tree was minimized.
  • Fixed an issue where values would not save on page types that contained deeply nested list of embedded components.
  • Fixed an issue where line numbers and help icons would not display on index view after first login.
  • Fixed an issue where the LinkSet element selector dialog would only return the first 128 results on initial load which would require users looking for a page out side of these 128 results to search within the selector dialog window.
  • Fixed an issue where removing Taxonomy Categories from a page or asset one at a time would only remove the last category.
  • Fixed an issue where an Asset element does not update the asset Path field when selecting a different asset.
  • Fixed an issue where there was inconsistent behavior with Spellcheck.
  • Fixed an issue where a page would not render if it referenced an asset that was not published.
  • Fixed an issue where Preview Option Sites drop-down list is never populated with options.
  • Fixed an issue where picking an asset with the asset search box would not create a link in TinyMCE.
  • Fixed an issue where Preview would display assets selected in Asset/Asset Navigation/Asset LinkSet elements that are not marked for publish when Show All Pages was disabled.
  • Fixed an issue where it was not possible to interact with List elements in Page Builder.
  • Fixed an issue where the View Details view would not load when an Asset Folder is selected in the Asset Manager.
  • Fixed an issue where it was not possible to upload an asset to an empty asset folder using the File Browser.
  • Fixed an issue where a new folder was created when downloading or uploading schemas in the Asset Manager.
  • Fixed an issue where expanding a List of components would cause the browser to become unresponsive.
  • Fixed an issue where login would fail when logging into the CMS in multiple browsers with a user account configured with Active Directory.
  • Fixed an issue where the File Browser would not load the previously selected asset in TinyMCE.
  • Fixed an issue where a processing error would occur when creating a link to an asset in TinyMCE.
  • Fixed an issue where DSS Link caches are not cleared from disk after clearing link element values.
  • Fixed an issue where some pages would revert to a previous version after check-in.
  • Fixed an issue where List items could be removed when the page was checked in.
  • Fixed an issue where embedding a component with a group of links with the same tag name will always use the value of the first link element in the group.
  • Fixed an issue where non-admin users could not select components for Component elements.
  • Fixed an issue where element numbering on the Edit tab would be thrown off after adding new list objects to a page.
  • Fixed an issue where uploading assets without extensions would have a period appended to the URL.
  • Fixed an issue where the blank option was not available when specifying a Navigation Type.
  • Fixed an issue where checking a page in to one publishing target will set the Current Version to all publishing targets.
  • Fixed an issue where pages would revert to a previous version after check-in in certain scenarios.
  • Fixed a UI issue where adding List Elements to Asset Descriptive Metadata would sometimes appear as a child of a different element in the schema.
  • Fixed an issue that prevented deletion of pages that do not have a Page Version from the Recycle Folder.
  • Addressed an issue where adding a new Embedded Component List Item via Form View will initially show only one of the component's elements in the list.
  • Addressed an issue where navigations within an Embedded Component do not expand on the DSS. 

Key Changes for Server Administrators

  • Upgraded Microsoft .NET Framework to version 4.7.2 which is now a software prerequisite.
  • CMS instances can be set up using the RavenDB Voron storage engine type and new setups default to the Voron storage engine type.
  • Improved memory management in the DSS environment.
  • CMS Content Freeze is automatically initiated during an in-place upgrade.
  • Setting up a new CMS site with the CMS Site Setup wizard using a site export will automatically disable replication for all publishing targets.
  • CMS will no longer keep a persistent copy of a checked out version of an asset on disk to conserve space.
  • The Dynamic Site Server default project no longer contains the forms authentication section in web.config.
  • Product installation shortcuts indicate the release version.
  • CMS and DSS Setup Wizards now display full build numbers.
  • Fixed an issue that prevented an upgrade from CMS 9 to CMS 10 due to Group elements missing a type value.
  • Fixed an issue where CMS Exports that contained folders with underscores would not unpack for new Site Setups which would cause thumbnails to be missing in the CMS.
  • Fixed an issue where CMS Site Setup would not complete if TLS 1.0 is disabled on the server environment.
  • Fixed an issue where duplicate custom-hook signatures for OnBeforeWorkflowAdvance, OnAfterWorkflowAdvance, OnBeforeWorkflowAdvanceAsset, and OnAfterWorkflowAdvanceAsset would be added during Site Upgrade.
  • Fixed an issue during Generation Upgrade from CMS 8 to CMS 10 where URL Map files that contained empty Path entries would cause the Generation Upgrade to fail.

Detailed Information

DSS RTAPI Now NuGet Deployed

The core DSS libraries are now deployed on NuGet. During upgrade or installation of a new 10.1 site where the rebuild DSS Preview option is selected all local RTAPI references will be converted to NuGet references. In the future, all DSS updates can be performed via NuGet. This update also vastly reduces the amount of DLLs that must be checked into source controls systems.

Local DSS application variable replaces Reference.SiteSearch for ISS custom controller

If your InSite Search (ISS) implementation relies on a custom controller, you can no longer retrieve the SiteSearch object via Reference.SiteSearch property. Instead, the Site Search instance is a DSS application variable as of CMS 10.1. This change was necessary to move to NuGet Based deployment. If you are using a custom controller, change any instance of the Reference.SiteSearch property to the DSS's local application variable. See Implementing ISS After CMS Site Upgrade for details.

Microsoft .NET Framework 4.7.2 Required

In order to support future DSS enhancements, Microsoft .NET Framework 4.7.2 is now a required software system prerequisite on the CMS server. The .NET 4.7.2 Developer Targeting Pack is also required on any development machine to build the DSS Preview or DSS project moving forward. The .NET 4.7.2 install requires a host OS reboot during installation.

Sites setup uses the RavenDB Voron storage type by default

In the near future, RavenDB will no longer be supporting Microsoft ESENT in their product roadmap and will only support the RavenDB Voron storage engine. To prepare for this change, CMS 10.1 introduces the ability to configure CMS sites using Voron. When setting up a new site using the Ingeniux CMS 10.1 Site Instance Wizard, the storage type will default to Voron and users will have the option change the storage type on new sites:

Currently, there is no option to switch from an Esent storage type to a Voron storage type for existing in place upgrades. If you would like to switch to Voron, it will require a manual process at this time.

New Element Type: XML Field

Previously, if users wanted to embed XML on a page, the user would have to upload an XML file to the Prebuilt folder and add an insert element to a page that referenced the XML file. This new element will allow users to embed a piece of XML directly on the page without having to reference a separate XML file. The new element uses an Ace editor that users can enter their XML. The XML is embedded directly under the field element during serialization. The Ingeniux DSS is required for this feature.

Setting up a new CMS site with the CMS Site Setup Wizard (Using a site export will automatically disable replication profiles for all publishing target.)

This feature was implemented so that when sites are setup outside of production (development or local environments), it prevents the accidental publish and replication to production DSS environments. While the replication profiles are disabled, the replication profile settings are still retained when they are re-enabled.

Known Issues

  • Customers who used pre-release builds of CMS 10.1 (10.1.11 through 10.1.33) and have exports from this pre-release range may encounter a site setup failure when using these exports if they include the Custom folder. This is due to a duplicate signature entry in the Custom\CustomHooks.cs file for OnAfterWorkflowAdvance an OnBeforeWorkflowAdvance. In order to use this export, you will need to modify the CustomHooks.cs file in your export package to remove the duplicate signatures.
  • Customers who are using InSite Search in their DSS Projects will need to upgrade their InSite Search packages to version 2.10.x pre-release or above in order for search operations to function after upgrading the project to Ingeniux CMS 10.

Who Should Upgrade

  • CMS 10.0 customers should upgrade to CMS 10.1.
  • CMS 9.0 customers should upgrade to CMS 9.0 SR8 prior to upgrading to CMS 10.1.
  • CMS 8.0 customers can upgrade to Ingeniux CMS 10.1 without an intermediate upgrade. CMS 8 customers with extensive custom hooks or custom tabs should carefully evaluate the level of effort required to migrate the JScript to C# syntax.
  • CMS 7.5 and earlier customers must first upgrade to CMS 8.0 temporarily before continuing to migrate to Ingeniux CMS 10.1.
  • 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.1, 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.1 product key if you do not have one already.
  4. Configure a test environment with CMS 10.1 using a replica of the CMS 8.0 XML content or CMS 9.0/CMS 10.0 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.1 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.

    Note: In most cases, DSS upgrades are now performed automatically by the upgrade wizard included in CMS 10.1. Customers upgrading their MVC template sites can continue to update the Ingeniux API DLL in their Visual Studio project manually, build the DSS site, and deploy the new files to the DSS code location. See the MVC knowledge base article, describing these steps.

  9. Implement the CMS 10.1 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.1 release.

License Key

Customers who upgrade to Ingeniux CMS 10.1 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.

More Questions

Please contact Ingeniux Support at 1.877.299.8900 or support@ingeniux.com with any questions regarding Ingeniux CMS 10.