What's new in Contensis

We've fixed an issue relating to the approve / decline link contained in the 'Send for approval' workflow email notification. Clicking on the link would take the user to the page, but would indicate the item had already been processed and would lock any further actions with it.

We've fixed an issue that was affecting access to Contensis when using versions of Internet Explorer 11 browser.

We've fixed an issue that related to copying markup fields containing links. Editing the link resulted in an error being generated.

We've fixed an issue which prevented publishing servers deploying updated files.

We've fixed an issue with the site view display when switching between different projects. This arose when adding navigation links to content across different project areas, where the tree view for the current selected project failed to display.

We've fixed a bug where content permissions for individually assigned users were deleted from a project when scheduled maintenance scripts were run.

We've applied a performance fix when using Azure AD login.

We've fixed an issue where entry listings failed to update when new entries were added. This was because the varnish cache wasn't being purged properly.

We've fixed a bug with publishing to multiple servers in parallel where the navigation XML and other system files weren't being published to all servers.

We've fixed an issue that arose when right clicking on a node where the attached entry's content type had been deleted.

We've fixed a bug with the CMS Editors group membership check during federated logins.

We now display the name of components once they have been inserted into the content type builder area in the user interface.

We've fixed an issue that arose if a user was not a member of the 'CMS Editors' group when using Azure AD to login to Contensis. The system failed to provide a message indicating the user wasn't authorised for access to that CMS.

We've fixed an issue relating to the 'Editor_SchemaExtendedValidElements' global setting. When set to exclude iframes, the setting failed to work as intended.

We've fixed an issue with thumbnail images when used in news module record pages. They would fail to save in the editor, resulting in the default thumbnail image displaying on published websites. This is now working correctly. 

No one wants to spend time recreating something that they've already done. We've added the ability to copy a content type, component and roles so you can focus on making the necessary adjustments without the effort of setting them up from scratch.

If you upload assets in an entry we now automatically publish them inline.

The assets will be published automatically if you are using the basic workflow, and approvers of entries can review any assets that will be approved in the Inline assets panel in the entry editor.

We've introduced the ability to group fields in your content types into tabs – making it easier for your authors to navigate and manage content in the entry editor.

This also introduces a new validation panel into the entry editor, allowing you to easily see and fix any validation errors in your content before publishing.

We've added a number of copy to clipboard buttons throughout the app to make it easier to copy Client IDs/shared secrets of API keys, as well as Field IDs and Entry GUIDs.

Reordering fields in the content type builder is now easier thanks to the introduction of drag and drop.

Crafting fields in a content type can be time consuming – especially when it comes to creating composers, which can contain many different types of fields. You'll now find a duplicate field option in the field action menu.

We've added the ability to search entries by content owner so you can locate content owned by a particular owner, or group of content owners.

We now show the name of a component when you add it to a content type, so you don't have to dig into the JSON to know which component you've added.