Recent product updates

Jahia 8.1.8 is a maintenance release primarily addressing security-related issues, that also includes various bug fixes and a couple improvements.

This version address incompatibility issues with Chrome 128+ and Firefox 130+

Apart from security and compatibility, improvements and fixes touch 4 main areas of the product:

• Imports: when a site is imported both in live and edit modes, the import is faster.
• Vanity URLs with a special effort on coherence and clarification related to status and publication / un-publication of said vanity URLs
• Sessions management : improvements to avoid Out of memory errors notably by limiting the size of Node Session Cache
• SAM (Server availability manager) : new probes were added that help customers to monitor the health of their Jahia instances, including Node Cache Load and Datastore node Health.

Jahia 8.2.0 is a feature release which comes with noticeable improvements, changes in our supported stack, library updates, module updates & other modifications.

Despite the array of new features and changes, the Jahia team has invested significant effort to ensure that upgrading from 8.1 to 8.2 is as straightforward as it can be. The main new features being optional, it is possible to adopt them progressively over a few months, post-upgrade, at your own pace.

Main new features

Jahia 8.2 provides updates for two main features of our CMS:

1. Page Builder, a new UI to manage content inside pages (in context editing).
2. JavaScript Modules, a new set of technologies to build websites with Jahia, without any Java knowledge. JavaScript modules leverage React/ JSX, rendered server side. Everything you need to know about JavaScript modules is available in the developer documentation. If you're a developer, you can also try out our new tutorials.

The Jahia team understands that adopting these new features will impact your projects and organization. However, rest assured that existing alternatives will remain, affording you the flexibility to try and adopt new features progressively, according to your specific needs and timeline. System administrators & developers can enable or disable Page Builder & the old interface Page Composer.

Other significant UX changes

• The Category Manager has been fully redeveloped to match our latest technology and UI standard.
• Editing the site configuration (virtual site node) is now available from Administration ⇒ Sites ⇒ "Sites properties". This new page has been added for consistency, and it is impossible to edit the site configuration using right-click ⇒ edit from the new Page Builder.

jCustomer 2

For organizations using jExperience and jCustomer, note that Jahia 8.2 requires jCustomer 2.x and jExperience 3.x. If you’re using Jahia 8.1.x, we highly recommend migrating to jCustomer 2.x before updating to 8.2. All required information is available on the page upgrading to jCustomer 2.x.

Technical changes

Detailed information is available on the page Upgrade guide to Jahia 8.2.0. Here is an overview:

• Our supported stack has been updated and is available in our customer center. A significant change is the addition of JDK 17 support and the drop of JDK 8 support. 
• Library updates:  Jahia 8.2 includes many library updates to benefit from their latest security fixes.
• Content types provided by Jahia: In the previous version of Jahia, many built-in content types were active by default when clicking “add content.” This caused some confusion for editors because there were too many types available. With Jahia 8.2, most of these content types were moved to a new  “legacy default content types” module. 
• Content Editor 4 module merged into jContent: Jahia versions 8.0.x and 8.1.x include two modules: Content Editor and jContent. Starting from Jahia 8.2.0, these two modules will be merged into jContent, using version 3.0. This new version includes the functionalities of the Content Editor module as well as the new Page Builder.
• JSON overrides: As part of the merge of Content Editor and jContent, JSON overrides, which allow modification of the edit form, have been simplified. Instead of two files, they now rely on a single JSON override file. This provides more flexibility when moving fields and fieldsets in the edition form. Previous JSON override files may still work, but there are breaking changes.
• External Data Provider: Jahia 8.2 introduces new interfaces to declare EDP using OSGi more easily
• Spring Framework & customizations done outside of modules: With Jahia 8.2, the use of Spring framework in modules is officially deprecated. In the same philosophy, Jahia is also deprecating customizations of the software done outside of modules. If some customizations cannot be achieved using modules or without Spring Framework, please raise the issue with our support team; and the product team will implement new extensions to allow you to use OSGI. Jahia is aware that these topics can have an important impact on your projects, which is why:
  • Spring Framework and non-modules customizations are still supported with 8.2 (deprecated, but supported).
  • No breaking change was added in 8.2 to enforce those policies.
• Hibernate: Before 8.2, Jahia exposed its Hibernate library. Starting with Jahia 8.2, Hibernate will no longer be exposed, and using it directly won’t be possible. If you need to connect to databases, we recommend using your own JDBC driver and SQL or embed your own framework. In future versions of Jahia, we’ll either provide a library fully compatible with OSGi or document how to use your own. If this is an issue for you, you can contact our support team, which works closely with our product team.
• The following modules have been moved out of the default build, moved to the Jahia store, and are not supported by Jahia anymore:
  • SDL generator - Note: Adding SDL files to your modules is still fully supported.
  • tabularList
  • grid
  • default-skins
• The Skins module has been removed from the default build. It is still supported by Jahia and there is no plan to stop supporting this module.
• Finally, portlets, which have been deprecated with Jahia 8.0.0, have now fully been removed from Jahia. 

Jahia 8.1.7 is a maintenance release primarily addressing security-related issues. 

This release includes a fix related to rewrite rules that were affected by a previous change (in jahia-page-composer 1.8.0 / Jahia 8.1.3.0), to only affect the rules related to Jahia edit mode.

Jahia 8.1.6 is a maintenance release that includes various bug fixes and a couple improvements:

• .webp thumbnails are now displayed in jContent
• The deletion modal has been reworked in jContent, however the one in Page Composer remains the same
• Developers can now find the target of setting panels, and jContent context menu actions, by looking at the html source of an element: this will simplify the registration of custom setting panels and actions!
  • See Adding settings pages and Understanding Jahia's component registry

Jahia 8.1.5 is a maintenance release based on the scope of 8.1.4.0, with added fixes regarding some XSS vulnerability issues identified in the back office interfaces. The breaking changes initially introduced in Jahia 8.1.4.0 have been removed from Jahia 8.1.5.0.

Jahia 8.1.4 is a maintenance release that includes various bug fixes. A couple third-party libraries have been upgraded to benefit from their latest security fixes.

In Page Composer, it is now possible to configure the threshold to display a single "Any Content" button in Page Composer to create content, instead of displaying one button per available content type, by setting the value in the jahia.ui.createChildrenDirectButtons.limit property, in the jahia.properties file. The default value has been updated from 3 to 5.

It is now possible to declare dependencies as optional. This is useful when “additional” features of a module require another module to be operational (e.g. a module providing a custom probe for the Server Availability Manager), but the module shall still be started and active even if these optional dependencies are not met. This is documented in the Package dependencies and exports page.

The Jahia 8.1.4.0 docker images can now be used for development purposes on macOS ARM architectures.

Jahia 8.1.3 is a maintenance release that includes various bug fixes. Several third-party libraries have been upgraded to benefit from their latest security fixes. It also comes with a couple improvements:

• Folders, and their structure, can now be uploaded directly by drag and drop in jContent! No need to zip a folder, upload it and then unzip it.
• The Crop / Rotate / Resize options for images are now available in a modal. The features and behavior remain unchanged, we have only changed the way they are presented.
• Module management administration screen:
  • Using configuration files, you can now disable the start/stop/deploy/undeploy module operations in this interface, for instance to prevent a critical module from being stopped. You can use version ranges, per module, to configure the list of disabled operations. This only applies for the Module management administration UI, as the OSGi console and module management API are not impacted by this feature.
    • Github documentation of this feature
  • You can display info or warning messages at the top of the module administration page, using a yml or configuration file
    • Academy documentation
• Introduced dedicated permissions for the admin node in Graphql Provider, this allows for additional fine-tuning of the access for mutations and queries using this node.
• Introduced a new permission in Personal API Tokens, to restrict access to "My API tokens"

Jahia 8.1.2 is a maintenance release that includes various bug fixes. Several third-party libraries have been upgraded to benefit from their latest security fixes. It also comes with a couple improvements:

• A definition check has been introduced, at module deployment, to ensure that the newly deployed versions are compatible with the previous one, and so with the already created content
  • it is however possible to bypass this verification and force the module deployment
  • A similar verification is also done when the started version of a module is using incompatible definitions, provided by a upper version of the module
  • Find about more in the Module definition checks page
• A new validInLanguage parameter has been added to the GraphQL API, to ensure that the returned nodes are not deactivated in the given language. Find out more in our GraphQL documentation page
• The publication screen now better highlights the number of items to be deleted as part of the publication

Jahia 8.1.2.1 is a patch release that includes critical bug fixes (especially one appearing when upgrading from 7.3.x to 8.1.2 in the Cloud and on-premises).

Jahia 8.1.2.3 is a patch release that includes critical bug fixes (especially one for a security vulnerability, see Security Patch - October 2022)

Jahia 8.1.1 is a maintenance release that includes various bug fixes. Several third-party libraries have been upgraded to benefit from their latest security fixes. See the release notes to find out more.

Jahia 8.1.1.1 is a patch release that includes security bug fixes (see Security Patch - April 2022):

• Backported security fix to our fork for Spring beans 3.2.18
• Upgrade of Tomcat version provided by our installer (from 9.0.55 to 9.0.62)

Jahia 8.1.1.2 is a patch release that includes the following bug fixes:

• Fixed issue with Jahia installation not possible without internet connection
• Fixed issue with cluster node synchronisation when using provisioning

Jahia 7.3.10 is the last planned maintenance release for Jahia 7.3, as it is entering limited maintenance. It includes various bug fixes, as well as the upgrade of a couple third-party libraries to benefit from their latest security fixes. See the release notes to find out more.

Jahia 8.1.0 is a feature release focusing on improving the security of the platform. Many libraries used by Jahia have been updated to benefit from their latest security fixes. The list of updated libraries is available in the release notes.

Jahia 8.1.0 also comes with the following noticeable improvements:

• A “structured view” is now available when browsing pages in jContent: this view allows editors to see the technical structure of a page, which can be useful in many cases!
• The “Publish now” button in Content Editor now only publishes the content being edited, and not including the sub-contents anymore. This is a major improvement, allowing you to only publish the new name of a page, without worrying about publishing the content of the page!
• The vanity url dashboard is now available in content editor
• The Personal API Token module is now part of the distribution

Jahia 7.3.9 is a maintenance release that includes various bug fixes. A couple third-party libraries have been upgraded to benefit from their latest security fixes. See the release notes to find out more.

Jahia 8.0.3.1 is a patch release that includes critical bug fixes:

• Workflows not visible when there are duplicated users/groups
• Upgrade issue when the server has no internet access (Fixapplier and Docker)

Jahia 8.0.3 is a maintenance release that includes various bug fixes and some notable improvements to Jahia 8:

• New permissions have been introduced to hide entries in the context menu for pages and content in Page Composer and jContent, allowing the configuration of roles with just the needed/used actions.
• New Docker images have been created for Jahia 8.0.3.0. The new images, improve integration with Jahia features (such as better support for database vendors). These new images are targeted towards production, development and discovery use.
• System administrators and dev-ops can now use our new provisioning API to orchestrate the startup of their Jahia. By providing a manifest detailing a sequential step of actions (install modules, sites, configure Jahia, execute scripts …) Jahia is able to reach production, in a reproducible manner, without any manual intervention.
• Content Editor 3.2.0 adds support for helpers for fieldsets and mixins and also includes bug fixes. Get Content Editor on here on the Store.

Documentation about the new images and provisioning API is available in a new DevOps section on the Academy

Jahia 7.3.8 is a maintenance release that includes various bug fixes. Several third-party libraries have been upgraded to benefit from their latest security fixes. See the release notes to find out more.

Jahia 7.3.7 is a maintenance release that includes various bug fixes. Consult the release notes to find out more.

Jahia 8.0.2 is a maintenance release that includes various bug fixes and some notable improvements to Jahia 8:

• Editors-in-chief and site administrators can now limit the number of items that can be created or displayed in a content list in Page Composer. Use this feature to reduce the number of buttons available for creating content in your pages and to make it easier for authors to drag-and-drop content to the correct location.
  • Read more about it at Changing the maximum number of items in a content list.
• System administrators can run integrity checks on a subtree
  An administrator can now provide the UUID of the parent node on which to run an integrity check in /tools/jcrIntegrityTools.jsp.
• Developer tools are now available in Jahia
  Developer tools have been moved from the /tools section to the main navigation in Jahia. No need to go to the tools anymore to execute a GraphQL query or generate a JWT token!
  • Introduced a new GraphQL editor
    We have also introduced GraphQL Playground, a more modern interface to build and execute GraphQL queries.
  • Read more about it at About Developer Tools
• Content Editor 3.1.0
  • Custom pickers are now supported through UI extensions. Read more about it at Customizing Content Editor pickers.
  • Images are now displayed in choicelists
  • Date picker now supports year selection

Jahia 7.3.6 is the latest maintenance version in the 7.3 family. Besides providing fixes for several issues, it comes with a couple security improvements:

• Enhanced protection against CSRF attacks
• The following libraries have been upgraded to benefit from their latest security fixes:
  • Spring 3.2.18
  • slf4j 1.7.26
  • Atmosphere 2.3.10
  • Camel 2.25.2
  • jodConverter 4.3.0
  • Shiro 1.6.0

System administrators will also be able to run JCR integrity checks on a subtree, instead of the entire JCR.

Jahia 8.0.1 is a maintenance release that includes various bug fixes and some notable improvements to Jahia 8:

• Content Editor 3.0.0 - Changelog
  • Synchronization between title and system name
  • Support for dynamic fields and dependent properties. For more information, see Creating dynamic forms in Content Editor.
  • Automatic ordering of content. For end-user information, see Automatically changing the order of content. For developer information, see Setting manual and automatic ordering of subcontent.
  • Support for custom selector types. For more information, see Creating custom selector types for Content Editor.
• Enhanced protection against CSRF attacks
• New permission that allows Jahia users to access the /tools section
  This replaces the Jahia Tool Manager user, which has been removed. For more information on the new System role that allows access to /tools, see Managing roles and permissions.

Jahia 7.3.5 is the latest maintenance version in the 7.3 family. Besides providing fixes for several issues, it comes with a couple improvements:

• The new clearLocks permission allows users to unlock content locked by other users. It is granted by default to server administrators
• Visibility condition being triggered using the server timezone, we are now displaying this server timezone when setting visibility conditions on content
• We introduced support for languages coded with 3 characters, following the ISO 639-2 format
• The compatibility with ImageMagick6 has been restored

The new Jahia 8 is here! It includes significant UI changes and back end upgrades.

Learn more in our dedicated Jahia 8 section

• New navigation menus and experience
  In Jahia 8.0 we’ve taken significant steps to update our navigation interface to make common tasks more efficient for users. The new navigation provides better organization and improved accessibility based on consistent placement of standard items: a new vertical navigation bar provides quick access to your sites, jExperience, server and site administration, and the user and workflow dashboards.
• New content editing interface
  Content Editor, initially released in 7.3.1.1, is now the default editing experience for content. No need to leave the editor to save and preview your changes. Content Editor integrates a preview of your content and the Save button not longer closes the editor anymore. Jahia in now easier to use when creating and editing content!
• Backend & Embedded Framework upgrades include
  • Karaf 4.2 and Cellar 4.1
    These upgrades introduce support for OSGi 6 and allows you to use Java 11 when developing modules
  • Jackrabbit 2.18, Apache Lucene 3.6.2, and Apache Solr 3.6.2
  • CKEditor 4.13
  • Spring 5.2 is now available, as well as Spring 3.2 for compatibility purposes
• Supported software environments:
  • We have updated our supported stack. You can check it out on the Downloads page!
  • Edge, Chromium based, replaces the IE 11 as our official Microsoft supported browser

Jahia 7.3.4 is the latest maintenance version in the 7.3 family. Besides providing fixes for several issues, it comes with two noticeable improvements. You can now:

• Unzip files from Content and Media Manager and zip files and folders
• Use accented and non-Latin characters in your vanity URLs as we have removed the limitation on only using letters and numbers

Jahia 7.3.3.0 is the latest bug fix version in the 7.3 family.

In this version we have improved the Anthracite theme, focusing on the consistency of the administration panels. Editors will also be able to copy or cut components from one tab and paste them in another tab. It is now easy to copy a component from Content and Media Manager and then paste it in Edit mode!

Version creation is now configurable, and has been tuned by default, improving performance during site import and publication. Find out more on the academy.

Jahia 7.3.2.0 is a rebranded version of Digital Experience Manager 7.3.1.1, and is the last release in the 7.3 family.

As most of our customers use the term "Jahia" to refer to our platform software (and even us internally), we decided to go back to its original name, used for the versions prior to version 7.0, and officially rename it into Jahia 7.3. This is part of the current rebranding we are operating at Jahia (the company!) to clarify our positioning as a Digital Experience Platform. Jahia, the software you know, is the core platform. Which currently integrates, by default, our CMS capabilities, that we rename into jContent. You can get some more details on "Why a rebrand" page.

Digital Experience Manager 7.3.1.0 introduces support for Content and Media Manager 1.2.0, support for custom GraphQL schemas using SDL, and the SDL generator module has been added to development installation modes. The release offers improvements to the automatic site import mechanism. In 7.3.1.0, you can now use internationalized site titles and unpublish in all languages. Other usability enhancements included searchable content in the search panel results in Edit mode.

Content and Media Manager 1.2.0

Content and Media Manager now available by default with DX 7.3.1.0 and includes improvements. You can now:

• Crop, resize, and rotate images
• Select and perform operations on multiple files and images
• Export content as an XML or ZIP file and import the content on another server
• Replace one file with another
• Access to translate engine in CMM

CMM also provides support for nested content, support for local mount points, performance improvements and an improved UI when uploading files.

The release also includes support for JDK 11 and Aurora (MySQL-Compatible edition).

Digital Experience Manger 7.2.3.5 is a hotfix that includes various bug fixes (release notes)

Digital Experience Manager has just updated to 7.3.0.0! With this update, we're introducing a new, and simplified, version of its user interface (Anthracite) to better improve user experience. This update is also required to utilize the new Content and Media Manager module, a unified interface that allows you to create and organize content and files.

Supported stack

Some elements of the supported stack have been updated:

• DX 7.3 now runs on Tomcat 9. JBoss 6.4 and Websphere 8.5 are still supported.
• DX 7.3 now supports MariaDB 10.x and MariaDB Galera.
• DX 7.3 now supports MySQL 5.7. Please note that while MySQL 5.5 is still supported in version 7.3.0.0, this support will be dropped in the next hotfix (DX 7.3.0.1).
• DX 7.3 still supports SQL Server 2012 and 2014. However, support for SQL Server 2012 will be dropped in the first service pack (DX 7.3.1.0 - not planned yet) and replaced with a newer version of SQL Server.

Noticeable fixes coming from DX 7.2

• You can now display untranslated content in edit mode by selecting "Show untranslated contents" in the Status menu
• You can now publish files in all languages (by using custom configuration)
• You can now disable emails when using publication workflows
• A new security update - We have introduced a token mechanism in the security-filter to protect API accesses

Digital Experience Manger 7.2.3.2 is a hotfix that includes the updates for the Anthracite user interface included in Digital Experience Manager 7.3. It also includes various fixes (release notes).

• You can now display untranslated content in edit mode by selecting "Show untranslated contents" in the Status menu
• You can now publish files in all languages (by using custom configuration)
• You can now disable emails when using publication workflows
• A new security update - We have introduced a token mechanism in the security-filter to protect API accesses

Digital Experience Manager 7.2.3.1 is a hotfix version, with a few noticeable fixes:

Core

• It is now possible to choose the version of jQuery to use between jQuery 3.3.1 and jQuery 1.12.4, via the configuration file.
• Configuration files can be overridden during module deployment (documentation)
• Modules cannot be started if their business rules (Drools) fail to compile

Anthracite theme

• Contrasts have been improved
• Icons are now displayed in the administration and in the site settings
• The thumbnail views of the document manager and file picker have been improved

Edit / Contribute mode

• Inconsistencies when using the "Work in progress" feature on multilingual sites have been fixed. A more explicit interface replaces the former checkbox when the site is available in several languages. More details are available in the "Work in progress" documentation
• The new dashboard to ease the management of vanity URLs (creation, deletion, move, publication) is activated by default. More information is available in our documentation about Vanity URLs
• By default for new installations (it does not apply upon migration), a drag zone is displayed at the top left of the content in order to prevent unwanted drag and drop. This setting can be modified by updating the configuration of your server.

External Data Provider

External Data Providers can now send events to DX. Find out how .

Content Editor 4.3.0 is a maintenance release, that includes various bug fixes. It comes with a major improvement: json overrides are no more global to the platform, and need to be enabled on a per-site basis, by enabling the module providing the override on the desired site(s). This allows more flexibility when multiple sites are managed on a Jahia platform.

Content Editor 4.2.0 is the feature release making it possible to reorder the different values of a multiple property. This version of Content Editor also comes with a light redesign to provide a better understanding of the various sections in long forms, as well as a new UI component for multiple selection in a list. The "Usages" screen, listing where the content is being referenced, has also been redesigned.

Content Editor 4.1.0 is the feature release providing redesigned pickers. This version of Content Editor also allows to select multiple item, and provide new PDF and video pickers. These new pickers are also highly customizable, either through a json override or by declaring new pickers.

Compatible with Content Editor 4.0.0, Copy to other languages 2.0.0 adds the possibility to copy the value of a property to other languages, selected by the user, before saving.

Content Editor 4.0.0 is the new major version for Content Editor, the interface used to create and edit content. It provides several major enhancements compared to Content Editor 3, most of them being based on the received user feedback.

• Content Editor is now displayed in a simpler modal when opened from Page Composer.
  • The various sections are collapsible, to make the interface lighter
  • Saving from the modal directly closes Content Editor
  • When editing content, it is possible to switch to the “advanced mode”, which opens in full screen and provides the same functionalities as Content Editor 3: preview, advanced options, etc.
• It’s not required anymore to save before switching languages! For projects available in several languages, you can now contribute the different languages, and switch between them, without having to save
  • You can use the copy to other languages 2.0.0 to copy a property in the desired language(s), again, without having to save
• Just like in 7.3, you can create several contents of the same type in a row, just by checking a “Create another” checkbox when creating a new content
• Automatic redirection: whereas you just created a new page/content, or edited one, once Content Editor is closed, you will be automatically redirected to the new page, or to the content you created/edited in the page. It’s especially useful when the content is located at the bottom of a page
• An edit button is now available in the notification displayed after creation, allowing you to quickly edit the content in case you realize you made a mistake or missed something
• Ctrl+S and Esc keyboard shortcuts can be used to save or close Content Editor

The full changelog is available on the Jahia Store.

With the “Copy to other languages” feature, contributors can copy the value of a content property from one language to the other languages enabled on the site. The interface allows the user to select which languages to copy to.

The option is available in Content Editor, the content edition interface, only for translatable properties. The content needs to be saved first, before using the “copy to other languages” feature, otherwise the option is disabled.

When using "Copy to other languages", the property is overridden in the selected languages.

Bug fixes and UX updates

When preparing an update of a web project (e.g. a new product launch or a marketing campaign), editors work on pages and content that can be spread across the website. The content releases module offer a convenient way to keep track of the content which has been created/modified, and published on the go-live.

The Contentsquare Accessibility Plugin is an accessibility tool, developed and maintained by Contentsquare, allowing site visitors to improve in real time the readability of a site to their own needs. It provides a text-to-speech assistant, which, once activated, reads the selected text. The accessibility tool also allows site visitors to customize a set of properties (including text size, font, contrasts, etc). Several pre-configured profiles are available to simplify this configuration, for instance for dyslexia, seniors, etc.
Simply enable this module on your site to embed the Contentsquare Accessibility Plugin on all pages.

• Included personal-api-tokens module in the jahia build
• Added the possibility to add scopes when creating a token

Bug fixes and UX updates

Vanity URLs can now be created from Content Editor , in the 3 dots menu:

Updated the Material theme used by the dashboard to match the Jahia 8 design

This module provides a panel in jContent > Additional > SEO > robots.txt allowing you to paste a robots.txt content

This release included a minor bug release.

This module makes tagging images easy so that you can easily search for them and avoid uploading the same image multiple times.

It uses machine learning provided by Amazon AWS Rekognition to automatically tag images, and can be used in 3 different ways in Jahia: 

• manually, when editing an image, in the tag field you can click "autotag" to trigger it
• on upload, for every new imagess
• using a GraphQL endpoint if you wsnt to tag a lot of images on your platform

With the personal API tokens module, you can use tokens instead of your credentials to make calls to Jahia APIs, such as GraphQL API and others.

The version 2.1.0 of the distributed session modules offers the ability to distribute sessions on all servers with hazelcast. This is a major eveolution since its version 1.0.0, as you won't need a Redis server anymore. More information on the academy.

This new version of Content and Media Manager provides bug fixes and comes with new features and improvements:

• Global design improvements
• Crop, resize, and rotate images
• Select and perform operations on multiple files and images
• Export content as an XML or ZIP file and import the content on another server
• Replace one file with another
• Access to translate engine in CMM
• Support for nested content
• Support for local mount points
• Improved UI when uploading files

This new version of Content and Media Manager provides bug fixes and comes with new features and improvements:

• Content marked for deletion are easier to identify
• You can directly drag-and-drop files into a folder to upload them
• It is possible to directly navigate to the parent folder / page of a search result
• You can open a page in edit mode from its context menu
• Developers can now provide "extensions" to Content and Media Manager. Find out how.

This version provides the following fixes:

• Fixed escape issues in file path or searched terms
• Use filename for downloaded file instead of technical name
• Nuxeo: Display folder name instead of technical name

The following reports have been added to the content reports module:

• New "Work in progress" report which lists all the contents currently marked as work in progress
• New "References" report which lists all the contents referenced by other content items

A new module, that includes the personalized news retriever, a DX component, that display best the news for a visitor. The best news are calculated according to 3 criterias:

• News that were not already read by the visitor
• News that were recently published
• News whose topic are matching the topics that the visitors is most interested in. These favourite topics are calculated from the tags of the news.  

Note: This module requires DX 7.2.2.0+, Elasticsearch search provider 2.0.1 and Marketing Factory 1.9.3. 

Local Site Manager (LSM) enables you to reuse pages and content from one site to another. LSM can be very useful for companies that have a global site with a lot of content and local sites that want to leverage this content. 

The Local Site Manager supports usage where a whole website, a few pages, or just some content is reused, using one or several languages. This module is free for customers with a DX enterprise subscription. 

• Content and files coming from external data providers can now be part of the Elasticsearch index, and therefore will be part of the search results!
• You can now use facets for your search results! Elasticsearch search provider 2.1.0 supports facets on text properties, including the type of content in the search result (e.g. page, news, event, etc.)

Content & Media Manager is a module that is both built on and extends the content functionality of Digital Experience Manager. It provides a single interface for editors to create and organize content and files. You can access and manage content in folders using the following functionality: preview, search, workflow and publication interfaces, administration panels, access to custom screens and features, and more.

In Content and Media Manager, you can:

• Access content that you create in the pages of a site.
• Access content from the /contents folder and files from the /files folder.
• Use the content and files from Digital Experience Manager sites and from external applications.
• Leverage Digital Experience Manager’s multilingual capabilities.