XperienCentral R49

During the development of R49, we have primarily focused on beta testing the new rich text editor scheduled for R50. Additionally, we have implemented numerous improvements and bug fixes in XC. We are postponing larger changes until after the release of the new rich text editor. As a result, for the first time in years, there are no specific upgrade instructions applicable to R49, making an upgrade to the next XC version easier than ever before!

Escrow deposit

The escrow deposit involves transferring code to an independent organization (NCC Group) so that, in the event of an ultimate calamity, affiliated parties are able to set up a correctly functioning XperienCentral environment using this transferred product code. This is a prerequisite in many contracts and agreements. It is our responsibility to deliver this in such a way that the Escrow Agent can deploy this code directly, which is also tested (and simultaneously indicates the replicability of our software). This escrow deposit has been made for R48 and deemed correct by the Escrow Agent.

Bugfixes and improvements

In addition, R49 contains the usual bug fixes and improvements. A number of noteworthy bug fixes and improvements are explained in more detail below:

Bugfixes

Able to select Design Template despite disabling this option (XC-1797)

In the "Design Templates" screen, you could use the option "Default Design Template is selectable" to indicate whether the default template should be selectable, for example when selecting a design template for an element. However, this option had no effect when selecting a design template for a page. This issue has been resolved in R49.

Discussion selection for a Content Item (XC-1808) 

After selecting a discussion for a content item and saving that change, it appeared as though the change had not been saved because the discussion field still showed "None". When another change was made and the content item was saved again, the discussion selection was undone. In R49, the change is correctly displayed after saving.

HTML in aria-label Attribute (XC-1863)

The aria-label attribute on an element of a webpage can play an important role in improving the digital accessibility of the page. In earlier versions of XC, several improvements have already been made to set the value of this attribute conveniently and logically. However, in specific cases prior to R49, it was possible for the aria-label attribute to contain HTML, for example, when assigning a link to an element. According to the W3C specification, HTML in an aria-label attribute is not allowed. In R49, HTML can no longer be included in the value of this attribute.

Selecting Fragments in a Form Section (XC-1897)

Since R46, it has been possible to select individual fragments of a form section while editing the main form holding that form section. This could lead to the unintended deletion of fragments from the main form. In R49, it is no longer possible to select the individual fragments of a form section from the main form (this can, of course, still be done when the form section itself is opened), preventing this issue from occurring.

Selecting Form in Current Language (XC-1674)

When selecting a form, previously all forms were shown, including those that did not have a version in the language corresponding to the language of the content item. From R49 onwards, only forms with a version in the same language as the content item are displayed.

Incorrect clone of Modular Content Properties (XC-781)

When copying modular content items or elements, the values of properties were sometimes not copied correctly. If the template on which themodular content item -or element was based contained a custom property, it could happen that the value of this property was not correctly copied. In that case, when modifying the property, not only the value of the copy but also that of the original was changed. This problem has been resolved in R49.

Improvements

Importing and exporting database references (XA-808)

When importing content items with database references, these references were not set. From R49 onwards, these references are correctly imported.

Display-on page for a download (XC-1728)

For various types of media items, a specific display-on page can be specified, such as for an article or an image. However, this was not yet possible for downloads. In R49, this capability has been added.

Setting link title for a new link (XC-722)

When creating a new link from the rich text editor (by selecting text and using the link button), it was previously not possible to directly specify the link title. Only after creating the link could the link title be adjusted via the Links tab in the properties of the content item. From R49 onwards, this can be done directly in the Create Link dialog.

SEO tab for image-based Modular Content items (XA-837)

In modular content items where the content type was based on the type "Image," the SEO tab was not displayed in the properties of the content item. As a result, alternative URLs for these content items could not be edited. In R49, the SEO tab has been added for this type of content item, allowing alternative URLs and other properties in the SEO tab to be edited.