What's new in Contensis

We've added support for uploading ATX (Animation Master Plugin Format) files to Contensis.

We've added support for uploading GML (Geography Markup Language) files to Contensis.

We've fixed an issue where deleting a group, or removing a group from a project would leave permissions in place on content types and templates.

We've fixed an issue that was preventing projects from being deleted from the cms.

We've fixed an issue where files were renamed incorrectly when uploaded inline.

We've fixed an issue with structured content pages where metadata wasn't being synced correctly for language versions.

We've fixed an issue where the QA service failed to work correctly for pages protected with Azure AD.

Fixed an issue where mapping taxonomies was failing in the delivery .NET client when a taxonomy node had been deleted.

We've fixed an issue where formatting was being retained when pasting HTML into the TinyMCE editor when using content types and entries.

We've made the project name readonly to prevent deployments breaking when the original name has been changed.

We've fixed an issue that related to the use of markup fields in components. If the component was set as repeatable within the content type, content within an entry would be lost if the component was repeated and the order was then changed.

We've fixed an issue that prevented users from being able to order entries by their sys.version dates.

We've fixed an issue that arose when attempting to save pages that had been opened to edit from the 'Edit this page' link. Clicking this link opened the page in a non edit version, which resulted in the error.

We've fixed an issue where pressing the enter key when the focus was in any form field, would default to the main search in a page.

We've removed the requirement for using [] brackets when searching arrays.

We've fixed an issue that arose when editing structured content pages which caused an error.

We've fixed an issue around getting a collection of content items that was introduced as part of the fix to optimise css assignments / unassignments for templates.

It's now possible to restrict who can create and upload assets to entries using roles. When a content type has an image/asset upload field you'll need to add an asset permission to any role that should be allowed to upload content.

You may have been aware of a hidden feature allowing you to see the JSON of a content type. We've given this editor a polish, and it now works alongside our content type validation to allow you to make edits to a content type directly in JSON. You can easily switch between design and JSON view using the toolbar menu.

You can now upload assets with the Management API – negating the need for our old WebAPI. This should make imports a lot simpler. You'll need to grant any API keys asset permissions to get started.

The new node methods in the Management API enable you to create and manage nodes without needing to open site view. If you already have a site structure in mind, want to import content from an existing system, or simply build a structure on the fly, our Management API provides the methods for you to make this a reality.

You can now preview entries against the URL they are attached to in site view, as well as any development preview you have set up for your content type.

Site view brings together your website structure and entry content. It provides a single place for site authors to create and manage content destined for the web – while keeping your content reusable.  

In version 11 when listing taxonomy using the API the default order was the order they were added to the database. This didn’t make much sense so we now order them alphabetically.

The content type ID and URIs for images, assets and entries are now automatically resolved and included in a Delivery API response. You no longer need to use the LinkDepth property to obtain this additional information. This makes it especially helpful when you want to display a link or an image on a page without making extra requests.

When you carry out a distance within search using the Delivery API, we now return the distance for each location from the specified geo point based on the unit of measurement in the query. This enables you to easily order the results.

The performance of searches through our Delivery API has been drastically improved. The processing that used to take place after the content had been retrieved from Elasticsearch is now done upfront, shaving time from your performance budget. In some cases we’ve seen an increase of upto 50%.

You can now set single selection taxonomy and list fields to use a dropdown. This should simplify some of those long lists in the entry editor.

When you're beginning to model a content type, you sometimes find yourself switching between the content type builder and the entry editor as you make adjustments.

• If you're a member of the content type administrators group, you'll now see an option to Edit the content type from the menu in the entry toolbar.
• You'll also see the option to Create an entry from the content type menu if you are a member of a role that allows you to create entries of the type open in the content type builder.

We've added a couple of extra items to the entry informational panel:

• Entry ID
• Content type name and API name

You can now filter entries by content type when adding a linked entry to an entry field that has multiple content types assigned to it. This makes for more precise searches when an entry field has many different content types assigned. 

• All tertiary menus across the interface have been updated to be navigable using the keyboard.
• CMD-S now saves changes in the entry, content type, components, roles and site view editors.

We've added support for assigning the entry slug in the preview URL option of a content type.

We've fixed an issue where the 'download as PDF' link failed to work. This now works correctly for standard and SaaS sites.