Home Knowledge Base Documentation CMS 9.4 Release Notes

CMS 9.4 Release Notes

Release Summary

Ingeniux CMS 9.0 Service Release 4 (SR4) includes 87 updates, including several new features. It also contains all features and enhancements from the initial CMS 9.0 release, the CMS 9.0 SR1 release, the CMS 9.0 SR2 release, and the CMS 9.0 SR3 release. Learn more about key enhancements and important upgrade information below.

Build Number

9.0.428

Change List

New Features & Feature Updates

When assigning pages in workflow to an individual user on initial assignment, only that user —and not the entire group— receives a notification.
A new capability to the Permissioned Workflow feature set has been added in System Options to allow restriction of the "Allowed to transition pages assigned to others" permission to apply only to members of the current workflow group.
A Group permission has been added to allow non-administrators to view and manage the Redirects app.
When advancing pages in workflow, the assignment list of users is now alphabetized.
The Redirects app now allows multiple entries with the same 'From' fields if they set on different publishing targets.
Added support for editing TinyMCE's Extended_Valid_Elements in the database to allow overriding and adding valid elements and attributes to TinyMCE

CMS & DSS Resolved Issues

Resolved several Run-Time Authentication (RTA) module issues that prevented some users from properly accessing protected content.
External links created in the TinyMCE editor that used paths starting with a leading '/' appended "HTTP://" before the URL.
Updated functionality for the Redirects app so that redirect values containing a trailing '/' for wildcards don't return a 404 error.
Submitting a publish to a publishing target that had pages unmarked for publish caused custom URLs to be removed.
Model.URL value was null in MVC preview.
Migrating a site from CMS 8.0 to CMS 9.0 caused component names to appear blank in the component picker.
The SmartCopy Paste as Clone option on the context menu displayed as "undefined"
Site Migrator did not migrate the value of the Max Depth attribute on Navigation elements.
Navigating to other pages in the Page View tab was not possible if the page was checked in.
The External Preview Provider option would not load external URLs.
Version numbers in the History tab were not accurate in some instances
Components were checked in and out on migration from CMS 8 - CMS 9+
Some non-ASCII characters were not properly encoded in the TinyMCE editor.
Importing users from Active Directory failed when the group containing the selected user was not also selected.
Non-administrators were unable to edit images even when granted edit asset permissions.
Parent embedded components and child embedded components that had the same name but different comp-types caused an error.
Users who belonged to multiple groups were not seeing the correct subset of menu options in the site tree context menu.
The Changed attribute was saving as server time instead of UTC time.
A reference component in a page that contained a taxonomy navigation with no category selected returned the referencing page's tagged categories instead of categories applied to the component itself.
Pages published using Multi-Format Output (MFO) were not being replicated correctly.
Editing a user account removed that user's SQL provider information.
The DSS site rendered the wrong XML for new pages when the schema was handled by a custom MVC controller until application reload
Expand on publish wasn't generating the correct XML results.
Sending email with SMTP relay configured for Office 365 services did not send email.
The CMS 8 -> CMS 9 Generation Upgrader changed some list items to text fields on migration.
Using the Undo Check-out feature made the reverted page appear to still be editable.
The Site Export tool did not export asset folders with lowercase names.
Very long file paths caused errors during publishing & replication.
Prevented Global Variable expansion from occurring on sites that didn't contain any global variables.
Current page creation rule settings lost from the page properties when editing other values on the page properties dialog.
Single file upload fall back behavior available for users without Flash did not work correctly.

InSite Search Resolved Issues:

The filtering logic for categories with InSite Search can now be either AND or OR logic
Searching for certain strings caused an application level error.
Queries containing some special characters caused an error.
Users couldn't filter by category with stemming turned on.
The number of returned search results did not match the specified value.
All navigation page nodes became indexed fields on fully expanded pages.
The indexed URL path to a result was not using the current URL.
Assets referenced within components were not merged as one result.
Keymatches didn't work when wildcards were set in the custom controller.
Wildcard search terms were ranked higher on the search results than boosted fields.
All elements with the same name on a page schema were concatenated into one field in the search results system's index.
Searching for certain keymatch phrases with wildcard search activated would cause an application level error.
Navigations set to expand on publish halted future re-indexing.
Global variables with static values were not displaying in search fragments within the search results.
Referenced and unreferenced asset results in InSite Search results did not have "Documents/" in the beginning of their path.

Important Information

Asset Controller & Global ASAX Update Required

The automatic upgrade system does not replace Global.ASAX or the Asset Async Controller. Clients must replace these files with the newest versions shipped in CMS 9.0 SR4. If these files have been modified they should be merged between the existing customized version & the new version.

Microsoft .NET 4.5.2 Required

SR4 requires .NET 4.5.2 to be installed on all CMS and DSS instances. The IGXSetup wizard validates that it's available before you may continue. Microsoft .NET 4.5.2 can be installed side-by-side with earlier .NET 4.5.x releases. DSS Preview and DSS instances can be both upgraded to .NET 4.5.2 automatically using the Ingeniux wizards. However, any custom projects or third-party libraries that are linked to a CMS or DSS project will also need to be re-targeted to .NET 4.5.2 in Visual Studio.

Windows 2012 R2 Requires Microsoft KB Update

All Windows 2012 R2 servers that have the November 2014 Microsoft update installed need to have an IIS level patch applied to them. See this Windows Server 2012 KB article for patching information.

Custom InSite Search MVC Controllers May Require Updates

Sites that implemented InSite Search in CMS 8.0 using a custom MVC controller need to slightly update their controllers, as described in this article.

Installation Wizard Changes

The Create Ingeniux CMS Site Instance wizard now supports using a CMS site export .zip when setting up a new CMS instance. The user created during setup is added to the imported site's administrator group. The Import Site wizard allows a CMS site export .zip to overwrite the existing CMS instance's database with a new content database. All content is replaced. The user specified is still added to the administrator group during import. The DSS Site Setup wizard can also perform upgrades to existing DSS sites and will upgrade and rebuild the selected DSS MVC project.

Default CMS Site Instance Installation Path

Newly created CMS site instances have separate \Site\ and \DB folders created under the \SpecifiedCMSInstanceName. The \Site folder contains all CMS application code. The \DB folder contains all application data. Existing sites that are upgraded won't have these folders.

DSS Path Recommendations

Due to ASP.NET and IIS restrictions, all DSS sites should be configured so that the content source location (PageFilesLocation) is outside the DSS application installation path.

Mark For Publish Behavior Change

Content items must be checked-in at least once before they can be marked for publish.

Start & End Date DSS Behavior Change

Pages with Start and End dates set in Page Properties have been filtered from links and navigations for many versions. In CMS 9 SR4+, they will also no longer be accessible by direct URL or xID. Expired pages will return a HTTP 404 friendly error page saying the page is not found until the page is no longer expired. Customers can redirect the URL to a different location for an alternate behavior.

Page Builder Requires Responsive Framework CSS/JS Inclusion

Ingeniux Page Builder requires templates (XSLT or MVC) to include the CSS of the responsive framework you have selected (by default, Bootstrap 3.x). Existing responsive templates may have these files included already. To enable Page Builder, non-responsive sites can add them to create columnar layouts within a fixed-width design; however, the Bootstrap or Foundation CSS may affect how the non-responsive sites render.

Last Generation Upgrade vs Standard Upgrade Wizard

Ingeniux CMS 9.0 has two different upgrade wizards. The CMS Site Last Generation Upgrade wizard copies an existing CMS 8.0 site; sets up a new CMS 9.0 instance; and migrates the content and the DSS Preview project from CMS 8.0 to CMS 9.0, leaving the original CMS 8.0 site untouched. (Learn more about this wizard in the CMS 9.0 Upgrade Guide.) The Site Upgrade Wizard upgrades from a previous CMS 9.0 version to the current version, similar to CMS 8.0.

Pre-Upgrade to CMS 8.0 Required For Earlier Versions

Customers using Ingeniux CMS 7.5 or earlier must first run the CMS 8.0 upgrade wizard before proceeding with a CMS 9.0 generation upgrade. Learn more in the CMS 9.0 Upgrade Guide.

Software Requirement Changes

ASP.NET 4.5.2 is now required. Because this framework doesn't support Windows Server 2003 and IIS 6.0, they are no longer supported for CMS 9.0. In addition, Ingeniux CMS 9.0 only supports 64-bit versions of each operating system when more then one configuration is available. Learn more in the Ingeniux CMS hardware and software requirements.

MVC 5 Allowed Syntax Changes

The Microsoft MVC 5 update no longer allows the @ symbol Razor syntax to be used within an existing @{ } braced Razor code block. Essentially, no nested @ statements are allowed. A compiler message may appear in the DSS Preview window indicating there is a syntax error in your view.

Hardware Requirement Changes

Ingeniux CMS now requires a minimum of 4 CPUs and 4 GB of RAM. The new version is multithreaded and performs significantly better when it meets the recommended base configuration of 8 CPU cores and 8 GB RAM. Larger sites may require more RAM. Learn more in the Ingeniux CMS hardware and software requirements.

RAM Usage Behavior Change

Similar to Microsoft SQL Server, the embedded NoSQL database used in CMS 9.0 reserves system RAM for potential future use, so the total memory allocated to Ingeniux CMS 9.0 processes is higher than it was in CMS 8.0. Additional resources may be required for very large sites.

Multiple CMS 9.0 Versions Side by Side Now Supported

Each CMS site instance runs its own version or build of Ingeniux CMS 9.0, so installing a new CMS 9.0 version on the server doesn't affect any previously installed instances.

Version 8.0 and Version 9.0 Side-By-Side Supported

All CMS 9.0 instances are unaffected by any existing CMS 8.0–based installations.

Visual Studio 2012 or Higher Required for .NET Developers

Since CMS 9.0 SR4 uses ASP.NET 4.5.2, all .NET development work requires Visual Studio 2012 or higher to edit and compile a DSS Preview or DSS project. You must install the .NET 4.5.2 Dev Multi Targeting Pack to edit .NET 4.5.2 projects in Visual Studio.

ASP.NET and MVC Automatic Upgrade and Rebuild Process for DSS and DSS Preview

The SR4 Last Generation Upgrade wizard now automatically attempts to recompile the DSS Preview Visual Studio project and update it to ASP.NET 4.5.2 and MVC 5. It returns information on the success or failure of the upgrade and recompilation. Recompiling manually, required with CMS 8.0, is still supported.

The CMS Site Upgrade used for CMS 9.0–to–CMS 9.0 build upgrades also updates and recompiles the DSS projects.

Internet Access Required

All CMS- and DSS-supporting library updates are delivered using the Microsoft NuGet packaging system, which downloads from the Internet. A DSS or DSS Preview upgrade and/or rebuild will fail without Internet access.

CMS Extensions/Customization Project

All CMS extension customization points—custom hooks, custom tabs, custom workflow actions, etc.—are now managed in a single Visual Studio project that has full debugging support. Learn more in the "How To" article for the CMS 9.0 development harness project.

Custom Hook and Custom Tab Migration

The APIs in CMS 9.0 have been migrated to a .NET 4.5.2 format using C# instead of the JScript used in CMS 8.0 and earlier. The custom hooks file is still in the /Custom folder. It is now a .CS file instead of an .INC file and uses C# instead of JScript. The CMS 9.0 CSAPI is publicly documented. The metaphors are very similar to those in CMS 8.0 and earlier, but the syntax is slightly different due to the change in language.

Custom hooks and tabs from CMS 8.0 and earlier won't cause errors in CMS 9.0 because they are disabled during migration until they have been syntactically updated to the CMS 9.0 format.

Developer training is available through the Ingeniux 430 API training course. Ingeniux 360 customers can get immediate coding assistance from Ingeniux site implementation engineers. Ingeniux Professional Services is available to assist other clients who don't have internal staff to perform the update. Please contact Ingeniux Support or your account manager if you need training or assistance.

XML Folder and Asset Storage Locations Changed

The XML folder is now located at \CMSPath\App_Data\xml. Individual xID files are, by default, no longer written to disk until publish. Each xID now has a property that allows it to be "serialized" to disk from the database if your CMS or site implementation relies on reading physical files from disk (not recommended).

Publish Folder Location Changed

The publish folder is now located at \CMSPath\App_Data\pub instead of being a child of the XML folder location. The published XML files in CMS 9.0 are identical to those in earlier versions.

Log File Locations Changed

All CMS log files are now located in \CMSPath\App_Data\LogFiles. The history.log file has been replaced with a unified audit trail.

Adobe Flash Required For Mass Upload

Adobe Flash 10+ is required for the mass-upload features in CMS 9.0. Users without Adobe Flash have single-file upload capability. Future updates will move to HTML5 upload to match Ingeniux Cartella.

Legacy Publish Deprecated

The only publishing process available in CMS 9.0 is the Dynamic Publish system introduced in CMS 8.0. The legacy publishing capability from CMS 8.0 was removed due to lack of use, performance, and standards compatibility. All CMS 9.0 customers use Dynamic Publish.

MSXML 6 Upgrade May Require Minor Template Changes

XSLT templates that call JScript extension functions that internally use MSXML 4.0–specific Prog IDs will need to be updated to use the MSXML 6.0 Prog ID. The XSLT engine in CMS 9.0 is now 64 bit, and there are no 64-bit versions of MSXML 4.0.

Internal User Database

CMS 9.0 has an internal user store in the NoSQL repository for users and instances that do not have Active Directory or LDAP access. During site instance setup, a new administrative login and password are created for configuration purposes.

Who Should Upgrade

All Ingeniux CMS 9.0 customers should upgrade as soon as possible. All Ingeniux CMS 8.0 customers on any service release can upgrade to CMS 9.0 SR4 without an intermediate upgrade. Clients with extensive custom hooks or custom tabs should evaluate the level of effort required to migrate the JScript to C# syntax. Customers on CMS 7.5 and earlier must first temporarily upgrade to CMS 8.0 before continuing to migrate to CMS 9.0 SR4.

Ingeniux Support will contact Ingeniux CMS OnDemand customers regarding the schedule for their OnDemand UAT and upgrade.

Upgrade Guidelines

To upgrade to CMS 9.0 SR4, follow these steps:

Review the Ingeniux CMS System Requirements.
Review the Ingeniux CMS 9.0 Installation Guide and/or CMS 9.0 Upgrade Guide.
Contact Ingeniux Support to request a CMS 9.0 product key if you do not have one already.
Configure a test environment with CMS 9.0 SR4 using a replica of the CMS 8.0 XML content.
1. If upgrading from an earlier CMS 9.0, use a replica of the CMS 9.0 Content Database
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.
If upgrading from CMS 8.0, run the Ingeniux CMS Site Last Generation Upgrade Wizard in the test environment to upgrade the site content to the latest version of Ingeniux CMS. If upgrading from CMS 9.0 to SR4, run the Ingeniux CMS Site Upgrade wizard instead.
Evaluate the site implementation in CMS 9.0 SR4 within the test environment.
Perform a full publish and set up a DSS site in the test environment to evaluate the latest version's DSS features.
1. In most cases, DSS and DSS Preview upgrades are now performed automatically by the upgrade wizard with CMS 9.0. Alternately, customers upgrading their MVC template sites can continue to manually update the Ingeniux API DLL in their Visual Studio project, build the DSS site, and deploy the new files to the DSS code location. See the MVC knowledge base article describing these steps.
Implement the CMS 9.0 SR4 upgrade in the production environment following the same process.

Ingeniux Support is available to work with your organization to determine the optimal plan and time frame for upgrading to the CMS 9.0 release.

License Key

Customers who upgrade from a previous version must obtain a new license key specific to CMS 9.0. Please contact Ingeniux Support at 1.877.299.8900 or support@ingeniux.com to request a new product key.