What's new in Contensis

We've now added Microsoft.Graph improvements to 11.3

We've updated the existing Visio content type to cater for .vsdx files.

We've made changes to Contensis forms in the following areas:

1. Ensure they now meet the WCAG 2.1 compliancy.
   
   
2. We've localised the 'Other' option against radio groups, allowing changes to be made in language variations.

We've made changes to authentication checks within a website context to improve overall performance.

We've fixed a bug that occurred in Safari when clicking on the 'edit this page' button in classic Contensis. This button now works as intended.

We've fixed some memory leak issues that were causing crashes and also affecting performance when using content types and entries.

We've fixed an issue where entry link arrays would not appear correctly in the UI if one of the array items was null.

We've fixed an issue where in certain scenarios, the FTP cleaner would leave empty folders on the file system. This could cause a site to break or affect redirects for the website.

We've fixed an issue that arose when adding an iframe into the source code view. This resulted in an unwanted ' ' being added automatically which would then break accessibility.

We've applied a fix for the image API path resolution.

We've fixed two issues relating to the navigation XML file. These are

1. an issue that prevented generation of the Navigation XML file. This was caused by forbidden and/or non-numerical characters used in file names and extensions. 

2. an issue that caused the generated file to be incorrect caused by a "." initial character in folder names located off the root of the site.

We've fixed an issue that related to mailto links specified as values in razor views. These were being overwritten with an encoded value, which was not desired behaviour.

We've fixed an issue that arose when attempting to access a url for an entry when a user wasn't logged into Contensis. Prior to the fix, the user would be taken to the login screen, and then to the home page of the cms, instead of being redirected to the entry.

This now works across all login scenarios.

Searching for a filename with an extension now returns the correct the results when using the Delivery API.

We've fixed an issue to ensure that the system does not delete the original slave folder when a master folder is moved out of a language or modifiable synchronised folder structure.

We've fixed an issue where new users or groups added to an AD setup were not visible in Contensis. 

Manually resetting the application cache would resolve the issue, so we've now put in place a fix to automatically reset the application cache when a new group is created.

We've added an ADFS/Azure AD fix for the security token generation.

We've fixed an issue that arose following a change made to Azure where it no longer allowed a trailing '/' on application id urls.

This change didn't affect existing installations, but would have affected any new integrations due to the wtrealm no longer matching.

The fix has been applied to wtrealm to fit the new format for Azure.

We've fixed an issue which stopped repeatable component content in the delivery .net client from being listed out.

We've fixed an issue where it was not possible to rename a linked entry field contained in a content type. 

We've fixed an issue affecting toggle buttons where validation rules were remaining in place after unchecking a toggle.

For an image field, if both 'Show the alt text field?' and 'Is the alt text required?' were set to 'Yes' initially, and then the first option was then set to 'No', the latter would then no longer be visible in the content type, but the validation would still apply i.e. alt text would still be required. 

We've fixed an issue with the asset fields of linked entries being returned as null by the delivery API search.

We've fixed an issue retrieving entries using the Delivery API that when specifying the entry description field to be returned but not its source field, both the entry description and its source field were returned.

We've fixed an issue with the Delivery API where the 'fetch.js' file wasn't minified affecting SEO.

We've fixed an issue where publishing entries for large complex content types (containing multiple composer fields) was preventing the entries being indexed in Elasticsearch.

We've fixed an issue where assets were not being removed from Elasticsearch when the folder containing them was set to non-published.

Fixed a rare error when loading an entry with a null composed field.

We've fixed an issue that was present in 11.3 versions of Contensis, when using IE11, where the display of some icons in the side navigation area was affected. This was caused by clipping on the SVG elements, which has now been resolved.

We've fixed an issue where the node delivery service was failing to load trees.

We've fixed an issue in Populo where it was failing to track PDF files.

Populo has been upgraded, and is now working correctly. 

We've fixed an issue evident in cms installations having multiple projects where the global setting Publishing_MaximimParallelProjects was set to allow simultaneous publishing of projects.

If multiple projects were publishing at the same time, the publishing queue would get stuck and publishing would fail to complete. 

Publishing is now working correctly, and we've fixed a couple of minor related issues too.

We've fixed an issue that mis-reported publishing dependencies for items of content. This was visible in the 'My Content' area of the dashboard on the cms homepage.

We've resolved an issue relating to the content review date functionality. This is now working correctly.

Fixed an error when searching for content with a very large query.

We've fixed an issue that occurred when content is synchronized and the links to content are resolved to their new content in the new folder. The system assumed that the content selector would always be content, not webpages, so resolved to the wrong thing.

We've made a change to prevent C# or VB files being viewed in dual view. This was because dual view creates a temporary version of the file in the same location which would have caused a site to fail in the event that the file was located in the App_Code folder area.

We've now added support for the .ATX file extension as a content type in Contensis.

We've fixed an issue that occurred when logging in via Azure AD, where an invalid account message was displayed.

We've fixed a localisation issue for the Councillor Details page area, where the party details were incorrect for language variations. This forms part of the Councillors and Committees module. 

We've added a new 'Contensis_authentication_always_apply_exclusions' setting to the cms config file to allow exclusions to always be applied, if required. 

We've fixed an issue to ensure that valid JSON is returned based on the form XML. The JSON will now list out 'allowedfiletypes' when assigned to a form upload element.

We've fixed an issue that occurred when using replicated folder synchronisation. It was caused by a navigation web control, added at sub template level, which did not have a Root Folder ID property set. This property is required by the content synchronisation service to find the equivalent slave folder.

We've also updated the content synchronisation code to log a more meaningful error message. 

We've fixed an error auto resolving images that either didn't exist or weren't published. This prevented pages from rendering correctly. 

We've fixed an issue where email notifications were not being issued for review dates assigned to content items. This is now working correctly.

We fixed an issue relating to table summaries for projects using different versions of HTML.

HTML 4 requires a table to have a summary, whereas HTML 5 doesn't. This fix ensures the summary option only displays when required in the table editor.   

We've addressed an issue where users were unable to programmatically retrieve the values of DateRange, Quote or Location fields from a component or component array when using the .Net Delivery API.

We've fixed an issue that arose when carrying out a filtered search in the entries listing screen. When the filter option 'Has published version' was set to 'No', the results failed to show entries that were in a draft state and unpublished. This is now working correctly.

We've fixed an issue relating to image fields where the dimensions were constrained to a fixed size with a 1:1 ratio. This prevented the upload of images.

We've fixed an issue where stylesheets that had their existing media type assignment changed to 'Editor' would continue to render on published web pages. This is now working as intended.

When previewing pages whilst using the personalisation panel, any changes to the personalisation selected options would not be reflected when the preview page was reloaded in the browser.  This issue has now been resolved. 

We've identified and fixed a memory leak issue relating specifically to the use of .svg images when using content types and entries in Chrome browser. The issue caused the browser to crash or run slowly. 

We've fixed an issue where changes made to an existing component e.g. added fields and their associated content, were not being reflected in the entry approval workflow screen. 

We've fixed an issue that occurred when using version history for an entry. If a user attempted to view a version that had been unpublished, the system would error stating 'Failed to get the entry'. This is now working as intended. 

We've fixed an issue where the use of the captcha feature on a form would generate an error on form submission. This occurred when using multiple projects, because keys from the first project were always being used, and not those of any subsequent projects where the form may have been used.

We've fixed an issue where the image API failed to resize images with an upper-case extension (e.g. .JPG).

We've fixed an issue where deleted images placed in the recycle bin remained visible in the image gallery area. Images could be added to an entry, but an error message would be generated when attempting to save the entry.

We've fixed an issue where new managed hyperlinks in pages with a schedule set for publishing at a future time, were being removed. This occurred when maintenance scripts were run.

We've addressed an issue to prevent the failure of maintenance scripts when cleaning up form posts in certain scenarios.

In addition, we have also fixed an issue with the image api that arose when resizing animated .gif files. This affected system performance too. Consequently, animated .gifs are no longer resizeable.

We've updated Contensis to remove the title 'Mr' that was automatically assigned to default system users when creating a new cms.

We've fixed an issue that affected the synchronisation of active directory groups into Contensis for cms installations with multiple user groups. Prior to the fix, some groups would fail to synchronise, preventing users from logging in to the cms.  

We've fixed an issue with the entry selector that limited the display to 25 entries. The selector now scrolls allowing all entries to be viewed and selected.  

We've fixed an issue that occurred for a specific scenario, preventing entries from publishing. The problem arose when editing an entry and adding an image field in to a composer, but not adding an image to it.  

We've fixed an issue with adding additional users to an existing synchronised AD group. Newly added users are now visible in the CMS after a re-synchronisation.

We've fixed an issue where the cms database re-indexing was failing. This was partly caused by database records referencing an older template version, rather than the current live version, and the number of rows in a database table. Scripts have been updated and improvements have been made to audit logging.

We've fixed an issue that occurred when upgrading Contensis from version 8.3 to version 11.3. This failed to populate the z-projects database table correctly, resulting in incorrect project information being stored.

It is now possible to set a default value of zero for number fields.

We've fixed an issue where incorrect default values for boolean fields were displaying. When a second or subsequent boolean field was added to a content type it would result in that field inheriting the default values from the first boolean field.

We've fixed an issue with the Delivery API that arose for entries containing component lists, where one or more of the added components had all fields left in an unpopulated state.

We've fixed an issue relating to location fields when viewed in the dual view (language translation) screen. For the originating language, the location field is now read-only.

We've fixed an issue that caused the inline editor to close when a user attempted to select an image.

We've fixed an issue relating to quote fields in content types and entries. 

In an entry containing a quote field where the field itself was not required (but the source field was) and both fields were unpopulated, and Save and approve was clicked, the CMS would display an unspecified error - 'failed to invoke the workflow event'. This was an API related issue. 

We've fixed an issue with managed hyperlinks containing long url's and querystrings. When editing a link changes now save as they should.

The Webp format now works in all versions of Internet Explorer 11.

Complete image asset data is now returned when using query fields.

We've fixed an issue relating to the publishing of the nav XML which failed to update correctly in some scenarios, resulting in the loss of information and/or availability of published web sites. 

We've made a number of performance and stability improvements to the publishing process.

We've fixed an issue with renaming files to match that of an existing archived file in the same folder. The system now shows a notification / dialogue message to the user to indicate why the name couldn't be changed.

We've fixed an issue where the version history tab would return an error in WYSIWYG content. The error occurred when viewing the history of pages which had been migrated to a new template if the previous template had been deleted. 

We've fixed an issue relating to the Remember me check box on the Contensis login screen. If ticked, the password was not saving users credentials, meaning they would have to reenter them again upon revisiting the site. 

We've fixed an issue relating to the Contensis search results screen. If a user conducted a search, and results were displayed, they were unable to re-order the results by clicking on the column headings.

We've fixed an issue that related to content types containing description fields. If the description was deleted from the content type using the UI, the description field wasn't actually removed from the JSON view resulting in an error.

We've fixed an issue where it was possible to delete repeatable fields, when present, from a default language entry, when viewing the dual view editor screen.

We've fixed an issue that occurred when viewing the image gallery screen for language variations. The image gallery filtered display would show images from the default language, in addition to those for the language variation in question. This was incorrect behaviour.

We've fixed an issue relating to the updating of images uploaded to Contensis, and used in entries. If an image was updated, the change would not be reflected at entry level - i.e. when editing the entry, it would still show the previous version of the image. This has now been resolved so that any change to the image, or reversion to a different version in the CMS will now be reflected in any dependent entries.  

We've fixed an issue where it wasn't possible to copy across date range values from one language version entry to another. 

We've fixed an issue that affected the publication of localisation changes. The process has been updated to ensure publication now works as intended.

We've fixed an issue that occurred when a quote field was set as non-required and the source for the quote was required. This prevented an entry from being published when there was no quote added, which was incorrect behaviour. Validation for the source field now only occurs when a quote has been added.

We've fixed an issue relating to the synchronisation of content for language variations. If a user added an asset e.g. image to the the master (default language) folder, the asset failed to copy to the synchronised language folder(s). This has now been remedied.

Fixed an issue where the forms builder wouldn't load correctly if you didn't have a license for Populo

Image transformations weren't being returned by the Delivery API when working with typed models

A recent update in Safari caused the audio player web control to show an overlay on mobile devices, that hid the page content. We have now updated the control to prevent this.

When editing a webpage or document it was possible to set a review date in the past. If a user attempts to do this now they will be prompted to change the date.

Folder administrators could create folder home pages but only system administrators could remove them. This has been changed so that folder administrators can both create and remove folder homepages in folders they manage.

When using ADFS to login to Contensis after 5 minutes you would be logged out. This has now been resolved so you aren't logged out unless you choose to logout.

We have addressed the following issues:

• Slugs were failing to resolve in the HTTP Delivery API when specifying a linkDepth
• Entries were failing to unpublish with the message 'Unpublishing assets is not supported'
• When returning to the entries list screen, filters which had been applied were not remembered
• Previewing an entry would throw an error if the preview URL didn't contain ?id={GUID}
• If you had more than one taxonomy repeatable field in a component then an entry would fail to save

The hyperlink management project setting (ManagedLinks_DeleteUnusedLinks) was not deleting all unused managed hyperlinks. It has now been updated to do this.

• When creating a content type, if you enable image uploading but don't specify an upload path you will now be notified when saving.
• When creating a content type, if you set an upload path it was not possible to unset it. You can now remove the folder path.
• Images failed to display in the image gallery when editing a language variation of an entry. This was happening when no images existed in the additional language. Regardless of this images now show correctly.
• When an entry was in read-only mode, it still looked like you could drag in images. The drag overlay has now been disabled in read-only.

If you opened Contensis in Firefox on a second monitor, popups would appear on your primary screen. They now open on the same screen as the main application.

When storing search text from PDF's there were cases where the content was being encoded incorrectly. This would result in some characters, such as copyright symbols, being stored as an unrecognised diamond symbol. This has now been rectified.

When installing Contensis we now set-up the IIS site for you if it doesn't already exist. This was causing issues if you had a preexisting site called Contensis with an uppercase C. We have now updated this so regardless of what your existing site is called the installer will run successfully.

When setting up a modifiable synchronisation, the root folder created as part of the sync wasn't copying over the folder properties permissions. The root folder now copies the folder properties permissions from the master folder, this is in line with the content type and template permissions which are already copied.

• If you added blank values to a dropdown field and saved a form, they would disappear from the forms builder so you couldn't subsequently remove them. This meant you could end up with multiple blank values on your live site. We now show the blank values in the forms builder so they can be removed.
• When trying to access a forms attachment when not logged into the CMS you would get an error. You are now prompted for a username and password and if entered correctly the download will begin. 

When opening images larger than the viewport in the image editor within an entry, you could end up with a vertical scroll bar present. This has now been fixed so you never see scrollbars when in the image editor.

If you selected an image in the WYSIWYG editor and tried to drag it within the placeholder to a new location, the image would disappear. This has now been fixed so an image can be dragged anywhere within a placeholder.

You can now view, compare, and reinstate versions of an entry. Version history is accessible via the more actions menu in the entry editor.

The new Image API provides an easier way to manage images for use on any platform or screen size. Now you can serve images that really meet the needs of the a users device, saving them time and bandwidth downloading files that are bigger than necessary.

View the API documentation

Images can now be cropped to a predefined size set by the new image dimensions property. Or a custom crop can be applied where more flexibility is required in content such as blog posts or news articles.

Its now possible to specify the dimensions of an image field in entries ensuring that the images selected by your authors meet the requirements of your content and design. When image dimensions are set on a field in your content type the image gallery will only return images that meet those requirements too.

You can now upload images and assets inline when creating entries, this saves you time and helps keep you in the flow of creating your content. To enable image and asset uploading you’ll need to enable the upload on the field in the content type builder.

Images/assets can be:

• Browsed for using your local file explorer
• Dragged and dropped to the field from your computer
• Dragged and dropped from the project explorer

You can now see audited lists of actions in the Management console. The following audits are reported:

• Users
• Groups
• Global Settings
• Taxonomy
• System

Get alt text from an image field.

Alt text can now be specified against an image field.

We now support alt text on image fields. This is especially important now we've introduced image cropping as the original alt text may no longer be relevant to any crop that has been applied. Alt text is an optional property on the image field and can easily be toggled on and off. You can set alt text to be required ensuring that your images are always accessible.

Its now possible to include the same entry multiple times on an entry field. This is helpful when creating step by step guides where the same content may be used in multiple steps.

We've introduced a form setting to forms that provides a way to automatically delete form posts after a set number of days. This helps to ensure you are not holding form data longer than necessary. These settings are audited and are visible in the audit screen for each form.

You can now carry out bulk deletion of form posts in the form search results table.

Get alt text from an image field.

Alt text can now be specified against an image field.

Image captions are now optional and can easily be toggled on and off.

You can now view the Node GUID in the information panel launched from the Project explorer.

• Icons across content types and entries have been updated to use SVGs. They should look a lot sharper on both retina and non retina displays.
• Toggle buttons have been improved, you can now click on the label as well as anywhere on the toggle.
• You can now open entries in a new browser tab by right clicking and selecting from the browser context menu, or scroll clicking on the entry edit buttons.