Release Notes

New widget interface admin.dashboard can be used to create widgets for the Admin Dashboard. Read more about implementation details here.

Site Mappings can now be used to customize the behavior of Image, Attachment and Component services Services.

Previously, custom content types required you to create a site, and link your app to the site before you could create them. Project Applications enable you to add apps directly to the project instead, and thus create custom content directly on the project root.

Also, controller mappings will now work on project level, which means you may also write custom previews without using sites.

All JavaScript XP core libraries have been rewritten to TypeScript. TypeScript definitions are published on NPM

Learn how to include references to TS definitions in your project here.

Virtual application behavior can be configured in application config

Shared Map framework is now part of XP. Shared Map сan be used to share transient data between nodes in cluster and/or applications. Both JavaScript and low level Java APIs are available.

Query DSL can now be used instead of NoQL for content and node searches. It also supports boosting of any expressions. Sorting can also be done with Sort DSL syntax.

Audit Log now logs Principals and ID providers modifications and global Application actions.

Default Content-Security-Policy (CSP) header is now applied for page preview. It improves Content Studio security but may introduce issues for pages which use inline scripts: inline scripts cannot be easily distinguished from XSS attacks and must be avoided. If you are experiencing problems with CSP header you can configure or disable it in Admin config. Controllers can provide their own CSP, if needed.

Attachment and Image Services now have a strict Content-Security-Policy header to mitigate possible XSS vulnerabilities. It can be configured in Portal config.

All http responses now have the following headers set:

As before, they can be customized in header filter config or turned off completely. Controllers can override them, if needed.

It’s now possible to implement custom content validators via Content Validators low level Java API. Custom error messages can be i18n-localised and will be displayed in Content Studio.

Periodical (cron-like) and one-time Job Scheduler is now available.

Content Layers enable automatic replication of content across dependant repositories. This feature can be used to implement multi language sites. JavaScript API is also available.

VHost API is now made public. Enumerate VHosts configured for your XP instances to customize URL handling.

latest option simplifies day-to-day snapshot/restore routines.

_sort and _score calculated meta fields are exposed in contentLib query results. Now it is possible to know how content items were sorted.

Another use of _sort calculated field is a geoDistance value. It calculates distance from provided coordinates to a geoPoint set in the content item.

In addition to the cluster freatures, AlwaysPreTouch has been enabled to avoid extra GC pauses on large installations.

XP now supports creating and working with content projects. Each project will create a separate repository, where content is isolated from the other projects. The repositories are named com.enonic.cms.<projectname>. Projects also introduce a simplified model in relation to permissions management and other default settings:

To take advantage of projects, you must also upgrade to Content Studio v3.

Dumps can now be streamed directly to a compressed archive to use less disk space, and speed up the process. Loads can similarly load data directly from a compressed archive. We now recommend always using compression when performing dump and load.

The updated auth API now supports request scoped logins, without having to manually modify the request context.

This is in particulary useful for handling modern stateful clients (i.e. using JSON Web Tokens), meaning that a server session is no longer created when logging in. Getting rid of sessions provide more scalability and reliability from a server side perspective.

Details are available in the auth API documentation.

The following improvements are also part of this release:

Any application can now store audit logs in a new common repository: "system.auditlog".

A core JS library Audit Library has been added to help you store and retrieve these audit logs

All successful state-changing operations, through the Content API, will create an audit log entry. In other words, all create/edit/publish/…​ in Content Studio or by using the content library will create an audit log entry This feature can be disabled by modifying the configuration file com.enonic.xp.content.cfg.

You can now retrieve an old version of a node by using the RepoConnection::get method.

Part component now supports a custom icon which will be used instead of the default one in Content Studio - in the Page Component tree and dropdowns with part descriptors. Just place an icon (in either PNG or SVG format) with the same name as the descriptor schema into the same folder. For example, if part/folder is called mypart then part descriptor is called mypart.xml and the icon file should be called either mypart.svg or mypart.png.

It is now possible to specify default headers set for every HTTP response via header filter. Default headers can be configured in com.enonic.xp.web.header.cfg configuration file via headerConfig property. If no value is specified set X-Frame-Options: DENY,set X-XSS-Protection: 1; mode=block,set X-Content-Type-Options: nosniff is used. Empty value disables Header filter.

The storage and CMS API now provide out-of-the-box highlighting functionality.

By submitting a highlighter definition together with your query, you will in return get text fragments where relevant search strings are highlighted. This is especially useful when presenting search results to end users.

Read more about highlighting

The Content API now introduces support for basic workflow capabilities. When creating or modifying content, workflow status may be specified. Currently the following statuses are available: IN_PROGRESS, READY,

The API will now prevent publishing of content unless it is in the workflow state READY.

For backward compatibility, if workflow state is not specified, it is equivalent to READY. Also, modifying content will keep the item’s existing workflow state.

Check out the content api for usage details

For an improved editorial experience, developers may now override the default <Display Name> text on a per content type basis. This helps make the content form more intuitive.

By adding the following line to your content type definition:

Editors will see the following in content studio.

Visit the Content Types documentation for more detail

The content API’s publish function now supports adding a message. This message is added to the "commit" entry that was added to the function with the release of XP7.

The publish message is builds on the commit functionality of the Node API.

Content studio enables you to see the publishing message from the version history widget.

Some of the improvements included in this release are:

In order for developers to better and more easily navigate the XP ecosystem, we created a dedicated portal. The portal contains

The brand new Enonic Command Line Interface - "Enonic CLI" was also released at the same time as XP 7. It is versioned independently for more frequent updates. The CLI not only replaces the old toolbox script, it also introduces new and flexible ways of installing XP and managing projects and development environments.

Installing CLI, Enonic XP, building and deploying your first app can now be done with a few simple commands, as described in the getting started section of the developer portal

The CLI is available for Mac, Linux and Windows. For more information, check out the full documentation.

The biggest conceptual change to XP is that the JVM is no longer required in order to run XP. XP 7 ships with JVM 11 embedded. As such, we now release native distributions of XP for the three major platforms, Mac, Windows and Linux. Expect future versions of XP to make more use of server native capabilities beyond the JVM. As always, you will never have to worry about portability when writing XP apps.

There are several reasons for this move:

With this change, XP is now available in SDK and Server version. The SDK includes the full JDK, whereas the server edition uses a slimmed down version of the JVM, and may be further optimized for production use.

Content Studio, the CMS editorial interface has been moved out of the XP core. It is now available as a separate application on Enonic Market

Content Studio can now be released more frequently than the XP core. Expect new versions of Content Studio to be released along with new features in the XP core.

For Content Studio release notes, check out the new documentation.

Even if Content Studio can be installed as a separate application, The XP core still ships with the content API and site engine that applications depend on.

The XP storage has been refactored for improved performance and disk usage.