Enonic XP 6.5 is a minor release, with cool new features and many improvements and fixes - there are no breaking changes
Enonic XP installers¶
A new download page is now available, providing native installers for OSX and Windows. The installers bundle the Java Runtime Environment (JRE) and as such simplifies testing of Enonic XP greatly. Developers are still recommended to use traditional Java installation as building applications will require access to the Java Development Kit (JDK)
Enonic XP installation docs Getting Started
New Text Component Editor¶
The Page editor’s Text component has finally been aligned with the htmlArea. It now provides all the powerful text editing capabilities you expect, such as tables, images, special characters, source mode and more. It is also more visually pleasing with a traditional ribbon at the top that can be exited easily by clicking the top right close icon.
Wouldn’t it be nice if you could create a component once, and re-use it across pages and templates? Well now you can! Thanks to the new concept of “fragments”, any single component (parts, texts, images and even layouts) can be converted to fragments. A new content type “portal:fragment” is available with this release, so when a component is converted to a fragment it is actually created as a separate content item. This means you can manage access control for it, and publish at will - just like page templates or other content items.
To get the optimal visual appearance when editing fragments, you will have to implement a fragment controller mapping (More about controller mappings below).
Inline image crop¶
The html editor now supports pre-defined image sizes and automatic cropping on insert. The sizes are Cinema (21:9), Widescreen (16:9), Regular (4:3), Square (1:1), Portrait (3:4), Tall (2:3) and Skyscraper (9:21)
Version history restore¶
Content Studio UI now supports rollback (and rollforward) in a document’s history. Simply restore a selected version and publish it!
Until now, rendering of sites required a 100% content driven approach, meaning you would have to create some content item in the path for anything to be rendered (with the exception of /_/services and /_/components). Also, if a content did exist, a page template or controller would have to be configured editorially first.
With controller mappings, developers can statically declare url patterns or content matches that will be triggered without any editorial setup:
Read more about Controller Mappings
Default values for input types¶
To speed up form population, the following input types now support default values:
- Portal Library - New function url() to create statically defined URLs.
- Marketplace installer UI now handles unlimited number of items
- Progress bar for marketplace installer while downloading
- Cleaned up presentation of htmlArea toolbar (aligned with new text component)
- SVG support for content type icons
- SVG support for content thumbnails
- More robust valueTypes conversion in forms i.e. from dateTime to date
- Added description field to users, groups and roles
- Support for pressing keys Y and N in close wizard dialogue
- Publishing dialogue - enable opening invalid items directly