From now on, users can view the summary of failed staging processes, which can help them to solve the issue(s) which caused the staging process to fail.
Release Notes
Generally Available (aka OOTB)
Using LAR files for export/import in the portal are stored in DM. These LAR files can increase the size of the DM significantly. We have changed this, so the LARs are not kept in the DM after the export/import process.
Generally Available (aka OOTB)
On LPS-136108: URLs using a virtual host are always reformatted on export and import, even in cases where they don't need to be the validation of the Web Content was added for Liferay layout URLs. Before this, there was no validation, so users could create their customizations where they could add different URLs to the Web Content's content. After the validation was added, some custom URLs became unable to be added to the Web Content. From user perspective this was a feature loss, so we decided to deliver a feature to make customers able to add their custom URLs to Web Content's content field. This feature is about adding a configuration for storing the user’s relative URL patterns. So custom URLs containing this pattern would bypass validation.
Generally Available (aka OOTB)
Before the Import process starts, users are now asked via a confirmation dialog if the user is sure about deleting application data . Also, we have improved the error message for Staging related references.
Generally Available (aka OOTB)
As a Site Template Administrator: template propagations are run completely in the background and background tasks are executed in a sequence. The LAR from the Site Template export is cached, so different Sites can reuse it.
LayoutSetPrototypeMergeBackgroundTaskExecutoralways uses the latest Template version for the propagation.- If there is already a queued background task for the Site, we don’t create a new one.
- If there is a background task in progress, we only create a new background task if the Template was modified.
Generally Available (aka OOTB)
- Deletion of property
upgrade.log.context.name. Now all upgrade related log lines are automatically tagged with the keyupgrade.component, which provides more meaningful information. - Upgrade Report is now compatible also with upgrade on startup, and it can be printed as Log Thread Context information.
- Upgrades log the result and the type of upgrade that has taken place after all the upgrade processes finish.
- New mBean available with upgrade on startup to obtain real time information about the status and the result of the upgrade.
Generally Available (aka OOTB)
Creation of a new property called upgrade.report.dl.storage.size.timeout that specifies the number of seconds that the upgrade report generation will wait for calculating the DL size before timing out. This property is set to 10 by default but it can be modified in the portal-ext.properties file.
Generally Available (aka OOTB)
Feature Status Change
Kaleo Forms was already in maintenance mode. It is now being moved to deprecated, so it can be removed at the same time as DDL in about a year. This solution is being replaced by Objects, Workflow, and Form Container Fragments.
Feature Status Change
The portlets that are in the Contacts module will be deprecated.
These are:
- Contacts Center
- Members
- My Contacts
- Profile
In the first step, the modules were pushed to the maintenance mode.
Generally Available (aka OOTB)
Maintenance
Feature Status Change
These modules are obsolete ones and are no longer being used. They have been moved to deprecate and later it will be removed.
Now you can create more detailed customer segments based on their specific actions. We have expanded our segmentation capabilities to allow you to segment your audience beyond standard website activities to include custom events. You can create highly targeted customer groups for more personalized experiences. Additionally, Liferay DXP now provides alerts when custom event criteria change, ensuring segment accuracy and relevance. Gain greater control over your customer analysis and the ability to deliver more relevant content.
Generally Available (aka OOTB)
A new out-of-the-box (OOTB) email notification template based on Objects. This template will be automatically sent to the order creator when an order status changes to 'pending'.
The notification includes:
Order number
Order date
Account name
Shipping address
Order item summary
Order total
We will move away from Commerce notifications and deprecate them and we will use Objects for the new ones.
Release Flag (opt-in)
Enhance your checkout experience by offering customers accurate UPS shipping costs based on their order details. Easily integrate this feature into your online store with our client extension available for purchase on the Marketplace.
Generally Available (aka OOTB)
Enhance Your Online Store with Adyen Payment Connector.
Liferay DXP now offers seamless integration with Adyen, a leading global payment platform. This powerful combination empowers businesses to accept a wide range of payment methods, reduce fraud, and optimize checkout processes. By simplifying payment management, Liferay DXP with Adyen helps you focus on growing your business.
Generally Available (aka OOTB)
This enhancement introduces configurable default permissions for newly created pages. Admins can set these permissions at both the instance and site levels. Instance-level settings are managed in a new Instance Settings panel, while site-specific overrides can be configured in the Site Configuration area.
Release Flag (opt-in)
The main change in this initiative is the new capability to control Analytics Cloud (AC) tracking through the cookie manager. We have updated the description of the Explicit Cookie Consent Mode to clarify that enabling this configuration via Preference Handling will disable Analytics Cloud tracking and other features. Now, if the Explicit Cookie Consent Mode is enabled, no cookies are set until the user agrees to their usage; otherwise, all cookies are set until the user opts out of them.
We have also introduced a new Utility Page, named Cookies List, which serves as a central hub for all cookies supported by Liferay. This page lists all four categories of cookies (strictly necessary, functional, performance, and personalization) and provides detailed information on each specific cookie, including its purpose and expiration date. For that, we have created new system objects to facilitate the management of cookies. If customers use additional third-party cookies, they can easily add new entries for these cookies, and they will automatically be displayed on the Utility Page.
Additionally, once a user is suppressed, their data is completely anonymized, making it impossible to trace any data back to a specific individual.
Release Flag (opt-in)
This initiative focused on enhancing user interface (UI) of both Downloading Reports and Path Analysis tool, establishing a cohesive design pattern across them. In particular, we committed to standardizing the presentation of Download Reports, encompassing various formats such as PDF and CSV, within the Downloading Reports Feature. This strategic investment underscores our dedication to delivering high-quality solutions that effectively address the evolving needs of our stakeholders.
Generally Available (aka OOTB)
Users can now efficiently locate images or videos by specific size categories (small, medium, or large) using the new filter feature on the Content Dashboard. Additionally, they can easily filter content or documents based on a range of dates for various lifecycle events, including creation, display, expiration, modification, publication, or review. This enhancement streamlines content management and improves user accessibility to relevant documents.
Generally Available (aka OOTB)
Users can readily spot documents & media that is not visible to Guest users through an icon, whether it's in list, card or table view or within the document editor. Additionally, this feature is accessible in the item selector, empowering users to discern which documents are not viewable by Guest users.
Generally Available (aka OOTB)
Users can easily identify and filter fields that are already translated and those that still need translation within the content editor. Additionally, they can choose to mark a language as translated even if some fields are not yet translated. Users also have the option to reset a translation to its default values with ease. These features will streamline the translation process and enhance efficiency.
Release Flag (opt-in)