Release Notes

A new widget provided by Content Studio+ enables creation of variants for a content item. Variants will be created under the original item and marked with a special icon. Variants can be managed (modified, published, duplicated etc.) as regular content items, then used in a 3rd party A/B Testing tool.

Read more about Variants here.

Content Studio 4.5.0 introduces support of applications for Content Projects. This will enable usage of content types and controller mappings defined in the assigned applications when creating or rendering content outside of sites. This is especially useful for headless content management as opposed to site-oriented approach.

You can assign applications to a new project inside the New Project Wizard, or do it inside the project settings form for existing projects.

Publishing Wizard and Publishing requests now support batch exclusion of dependant items. "x" icons have been replaced with checkboxes which can be checked off for multiple items, then confirmed with the "Apply" button which will refresh the dependant list. If checkbox next to dependant item is disabled it means that this item is required for publishing. Excluded items can be added back to the list from the "Show excluded icons" mode.

Settings, Schedule and Permissions icons were moved from the Content Editor form’s navigation toolbar to the "Details" widget. Fields from the Settings section (Language and Owner) were moved inside the "Properties" section of the widget, while "Schedule" got its own dedicated section right underneath "Properties". Permissions can be modified from the dedicated section of the same widget, as before.

Previously, clicking "Localise" for a content item in a layer would set the layer’s language in a content but not save the change, which means that the content wouldn’t really be localised until user explicitly clicked "Save". Starting from this release, "Localise" action will set the language and save the content, instantly localising it.

If the list of items to be published contains invalid items or items that are still in the "In progress" workflow state or items that current user is not allowed to publish, the warning section will be shown on top of the dialog, displaying all failed validation checks. The "Publish" button will then be disabled and "problematic" items will be shown on top of the list.

User can use links next to each validation check to exclude these items from the publication. All the validation checks will be re-run on every change of the publication contents.

If all the checks have successfully passed, the "Publish" button will be enabled and the warning section will say that everything is ready for publishing.

If any of the items in the Archive/Delete dialog has an inbound dependency (is referenced by another content), a warning will be shown on top of the dialog and the action button will be disabled. User can either click "Ignore inbound references" link to ignore the warning and proceed with archiving/deletion, or click "Show references" link for every referenced item and remove the references (the dialog will be automatically refreshed).

Previously, to display modifications of a published content user had to use the "Version History" widget and compare versions. With the new "Show changes" shortcut link displayed in the Content Navigator’s and the Content Wizard’s toolbars such comparison can be done in one click.

Content Selector inputs got []` icon next to the selector dropdown which enables adding a new content to the selector without having to go back to the Content Navigator. If the Content Selector is configured (via `allowContentType` config) in such a way that it allows only one content-type, `[] icon will instantly create a new content of this type and open a new Content wizard tab. Otherwise, user will be asked to select a content type from the "New Content" modal dialog.

Marking content as ready will now automatically open the Publishing wizard for this content.

The Insert Link dialog in the HTML editor has been completely revamped to support relative URLs, parameters/anchor for internal URLs and advanced handling of media links.

Here’s what’s new:

This experimental feature that has been introduced in Content Studio 4.1 has now been thoroughly tested in cluster environment and turned on by default.

In collaboration mode Content Wizard’s header will display avatar icons of all users simultaneously editing the content or simply having it opened.

Creation of a new content project is now done by completing the multistep wizard. This dialog will now automatically pop up for a user that doesn’t have access to any existing projects upon logging into Content Studio.

Support of RTL (right-to-left) languages have been added for TextLine, TextArea and HtmlArea input types, as well as for Text components. Currently supported RTL languages are: Arabic ('ar'), Dhivehi ('dv'), Persian/Farsi ('fa'), Hausa ('ha'), Hebrew ('he'), Kashmiri ('ks'), Kurdish ('ku'), Pashto('ps'), Sindhi ('sd'), Urdu ('ur'), Yiddish ('yi').

If content language is set to one of these languages, inputs of types TextLine, TextArea and HtmlArea, as well as Text components inside Page Editor, will be set to right-to-left direction.

icon now compares the selected version to the previous one, not to the current one.

The widget now displays content versions created for Permissions update, Sort and Move actions.

The Filter panel have been expanded with the following parameters:

The list of Content Types by default shows the 5 most popular types. The entire list can be expanded with the "Show more" link.

Free-text field can be used for search by content id.

Content Studio 4.1 enforces Content Security Policy (CSP) to prevent cross-site scripting, clickjacking and other code injection attacks resulting from execution of malicious content in the trusted web page context. CSP can be configured or turned off completely (except for Page Editor) via config file.

Support of new widget interface allows injection of "full-screen" widgets which will be seamlessly added to the Content Studio top menu.

In collaboration mode Content Wizard’s header will display avatar icons of all users simultaneously editing the content or simply having it opened.

"Set Default" button will be displayed for Date, Time and DateTime inputs with <default> value set in the schema.

It’s now possible to change styling of Numbered and Bulleted lists in HTML Area by right-clicking the list and selecting list style from the dropdown.

Archive now effectively replaces Delete as default action for removing content that is no longer needed. When archived, content will be moved to a separate storage where it can safely be restored from, rather than physically deleted. It’s still possible to immediately delete content using the dropdown menu in the Archive dialog.

Full documentation of the Content Archive feature can be found here.

When archiving/deleting content it’s important to visualise if the content about to be archived/deleted has any inbound references as the archive/delete operation may potentially break rendering of the content structure. Previously, inbound references were displayed only for the items selected for deletion (but not for their descendants). Starting from version 4.0 visualisation of inbound references in the Delete/Archive dialog has been improved: a special icon will be displayed for all items that have inbound references, and if at least one of the items is referenced then there will be a separate warning about that at the top of the dialog.

TextLine and TextArea inputs are now automatically checked for spelling errors.

Read more about spell checking here

By default, content path in the Content Form will be auto-generated based on a value typed into the display name field and all the international letters will be automatically transliterated into their english equivalents (for example, "/øåæ" becomes "/oaae", "/рыба" becomes "/ryba" etc.)

It’s now possible to turn off automatic transliteration by setting contentWizard.allowPathTransliteration property to false in the Content Studio’s config file.

Image Component has been deprecated in favour of Text Component which can be used for embedding images and has a richer UI than Image Component used to have. Existing image components on your page will continue working, but you won’t be able to add a new one.

When docked, Context panel will responsively change its width based on available space with 25/75 ratio relative to the Preview panel (in the Content Browse view) or Page Editor panel (in the Content Wizard view).

Height of all selector dropdowns has been increased to allow for more visible items (9 instead of 4 in Content selectors and 3 in Image selectors).

Admin API has been moved from XP core to Content Studio and starting from version 4.0.0 resides directly in the Content Studio app. This will help us release Content Studio without having to change XP and release a new version of the platform. URLs of Admin API have been changed as well. Admin API was never intended for external use, but beware of that if you had any custom integration with Content Studio’s Admin API then this will stop working from version 4.0. As this migration affected XP as well, Content Studio 4.x requires XP 7.8.0 or higher.

Due to security concerns, we have removed the configuration setting allowing <script> tag in the Rich Editor. If you are using inline scripts in your HtmlArea inputs or Text components, those will be stripped out the next time you save the content.

Internet Explorer is no longer supported by Content Studio.