This feature applies the GDPR rules to the object entries. When the admin chooses to delete User's Personal Data, the object entries related to that user will also be deleted.
Release Notes
Ability to filter the user agent (all, human, bot) for each redirection pattern, in Configuration.
Option of rating added to Folders and the endpoints for Documents rated by me, Folders rated by me have been created.
Pleae check the Content Security Policy by clicking here.
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.
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.
- 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.
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.
LayoutSetPrototypeMergeBackgroundTaskExecutor
always 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.
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.
This is the Staging related implementation of a bigger change. On the Staging side, the LXC Client extensions (Remote apps) could be handled. To make this feature completely working, LPS-182183: Export/Import of FrontEnd Client Extensions is also needed.
Two new configuration options were added:
- The first one gives the users the chance to automate an existing feature, which improves performance.
- The other one is about displaying the Advanced Staging configuration screen to the users, improving usability.
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.
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.
We introduced a new feature to streamline workflows with 1:1 relationships between objects! Now, users can create and update nested objects directly from the primary object's CRUD views, and enjoy seamless delete and view operations translated from the Data Set Manager (DSM). This update makes managing data smoother and more efficient.
Add changeTrackingEnabled to the standard rest-config.yaml
so that services must specify Publications support. This will simplify the process of enabling change tracking for future Headless APIs.
Data Migration Center users should be sufficiently notified if actions can only be made in Production, since DMC does not support Publications yet. |
Some upgrade processes may not consider the ctColectionId
column which may generate inconsistencies for customers using Publications, especially for older versions.
Liferay has expanded GraphQL capabilities to match the functionality of REST APIs for managing object entries. Users can now transition object entries from Draft to Approved status using GraphQL, providing more flexibility and control within the development process. |
Liferay DXP provides a variety of developer tools that include a robust build script framework, lightweight CLI utilities, and IDE tools. We have recently released new versions of Liferay Workspace and the IDE tools, which include Liferay Developer Studio, Liferay Eclipse Plugin, and Liferay IntelliJ Plugin. The main benefits include:
Alignment with the platform itself: The tools now support our quarterly releases, giving access to development on Liferay DXP's latest features.
Latest Java version support: Compatibility with JDK 17 and 21 provides developers with enhanced security, improved performance, and the newest capabilities of the Java platform.
- Upgraded development environment: Support for Gradle 8 enables improved build automation features and performance.
For making the Sign In portlet related functions easily customizable for the end users we want to simplify the portlet as much as we can. We need to remove all it’s configuration or functionality that can be handled in higher level.
Currently, the customer has to resort to email reports to see their autoscaling. We are making this information much more available and searchable, allowing the user to better understand their autoscaling behaviour.
External Reference Code is now supported in Roles, Specification Groups, Specification Labels and Addresses.
It is also now possible to use the ERC to update and delete these entities via their headless APIs.
Additional ERC support for linked entities has been added when creating new Options, SKUs, Accounts, Catalogs, Orders, Shipments and more.
This new feature allows streamlined return processes for both buyers and sellers.
Buyers can easily initiate return requests directly from their order history, specify the reason for the return and request a refund.
Returns Managers, within the Returns admin pages, can review the return details, communicate with customers, and issue refunds with just a few clicks.
Feature Status change:
Now the possibility of Export/Import Frontend Client Extensions is available by default.
Users can now easily filter images and videos by resolution (small, medium, large) or aspect ratio (wide, tall, square) directly from the Content Dashboard.
|
Users can select and reorder categories for a blog’s friendly URL, so they can preview the order of the categories in the friendly URL.
The configuration settings for "Autogenerate Structure Key" and "Autogenerate Template Key" have been moved from their previous location in System Settings > System Scope > Administration to a more instance-specific location under System Settings > Web Content > Virtual Instance Scope > Web Content, appearing as the first options after "Custom Token values." These options allow instance admins to control whether structure and template keys are automatically generated at the instance level.
The Web Content Editor now includes an autosave feature that automatically saves changes in real-time as users edit, storing the content as a draft. This also allows users to easily undo or redo changes as needed. With this enhancement, manual saving is no longer necessary, ensuring continuous backup of content and minimizing the risk of data loss. Content creators can now focus on their work without the worry of losing progress or facing interruptions.
|
External reference codes are now generated for Blogs Images and Document Shortcuts.
ERC can now also be used to update and delete these entities via their headless APIs.
Smoother Workflow for Publication Editors
The new toolbar offers real-time insights to help editors stay focused and efficient. We have improved the toolbar to provide essential context, including current publications, potential conflicts, and change history.
Enhanced User Safety and Transparency in Publications
We have implemented safeguards to guide users through complex interactions and provided clearer information about changes in the Review Changes screen.
Boost Liferay’s platform with drag-and-drop, multi-selection, and cut/copy/paste features for easier field and fragment organization.
Enabling users to be notified externally by allowing email notifications when a new user is assigned to a publication.
This feature ensures that theme CSS client extensions "just work" out of the box when referencing images from the base theme. It reduces friction in the development process, increases reliability, and provides a more seamless and predictable experience when customizing their Liferay environments.
How it works:
Simplified Image Management:
Developers no longer need to manually handle or configure paths for images included in the base theme.
Relative paths (e.g.,
../images
) can now directly reference these images, reducing complexity and errors.
Out-of-the-Box Compatibility:
The feature ensures that theme images are automatically included during the build process via the
assemble
step.This means that after deploying the theme CSS client extension, image references work seamlessly without additional configuration.
Create smooth multistep forms directly in the page builder with Liferay’s new fragment—making complex processes simple and intuitive!
Liferay DXP makes it easy to create dynamic, multi-step forms. Simply add a stepper fragment to any existing form to transform it into a multi-step journey. You can then organize your form into different steps, moving inputs between them as needed. Users can easily navigate through the steps using the step menu or form buttons, which you can customize to fit your needs.
Enable JavaScript Client Extensions within SaaS environments to enhance customization and flexibility for administrative tasks, allowing tailored solutions directly within the platform.
Data Sets now offer even greater customization power. Admins can directly add manual query parameters to the endpoint URL, enabling fine-grained control over data retrieval.
This flexibility allows you to:
- Filter Data: Apply specific filters to narrow down the results
- Select Fields: Choose the exact fields you want to retrieve
- Flatten Responses: Simplify complex data structures
- Search for Specific Terms: Find relevant information quickly
By tailoring the endpoint response, admins can provide a more curated and user-friendly experience for end-users.
Behind the Scenes:
The platform seamlessly reconciles these manual parameters with those generated by:
- Admin Configuration: Fields and Actions tab settings
- End-User Interactions: Filter and sort options selected in the UI
This ensures a consistent and efficient data retrieval process.
On top of that, admin users can also add or map fields manually to be displayed in the Data Set, so they will be able to bring the information back for those endpoints that don’t have the fields properly typed in the response.
Liferay Cloud currently supports Java JDK 8 and 11, but the industry is moving towards newer Java versions like JDK 17 and JDK 21. To ensure that Liferay Cloud remains modern, allows our customers to leverage the newest security patches, and boosts overall performance.
When the access token is near the expiration date, the portal sends notifications to the System Administrator about it.
Feature Status Change
Enabling this feature will allow users to dynamically populate fields using expressions with information created from data filled and provided by other fields.
Feature Status Change
The Forms feature is going into maintenance.
Feature Status Change
The Commerce Accounts feature is being deprecated and will be removed in the future. To ensure data continuity, we recommend transitioning to Portal Accounts.
Feature Status Change
|
The Commerce Notifications feature is being deprecated and will be removed in the future. |
Feature Status Change
The Commerce Modals feature is being deprecated and will be removed in the future.
Feature Status Change
We have implemented a new translation status feature in the web content editor, labeled "Translating," which provides information about the number of translated fields and those still requiring translation. This feature helps users quickly identify areas needing translation. Additionally, all translatable fields, including metadata, are now conveniently displayed on the left side of the screen, reducing the likelihood of overlooking them.
Feature Status Change
The Wiki feature is being deprecated and will be removed in the future. Wiki and its related widgets are now subject to the deprecation flag LPD-35013. To ensure data continuity, we recommend transitioning to alternative content management solutions like Liferay Objects or Web Content.
Feature Status Change
Users can now set a display date for the documents so they can scheduled them to be published in the future, just for one document or when uploading multiple documents.
The new Date Range and Range aggregation types unlock powerful search capabilities for your Liferay assets, including Web Content Structures and Objects.
By configuring any date or numeric index field, you can:
- Group and Filter Results: Create dynamic search filters based on specific dates or numeric ranges.
- Customize User Experience: Offer flexible search options with predefined ranges or custom input fields.
- Visualize Data Effectively: Leverage out-of-the-box display templates for a seamless user interface.
Think of Date Range as a versatile extension of the Modified Facet. You can now select any desired date field to refine search results precisely.
Note:
The functionality of the Date Facet widget was introduced under a Developer Feature Flag in LPS-153839 2024.Q1 has been integrated into the Custom Facet and is now available as GA. The Date Facet widget is no longer available.
Synonym Sets now also supports the following languages (locales) out of the box:
Portuguese (Brazil):
pt_BR
Portuguese (Portugal):
pt_PT
Italian:
it_IT
Arabic (Saudi Arabia):
ar_SA
Catalan (Spain):
ca_ES
Catalan (Andorra):
ca_AD
Catalan (Spain, Valencian):
ca_ES_VALENCIA
Chinese (China):
zh_CN
Chinese (Taiwan):
zh_TW
Dutch (Netherlands):
nl_NL
Dutch (Belgium):
nl_BE
Finnish (Finland):
fi_FI
French (France):
fr_FR
French (Canadian):
fr_CA
German (Germany):
de_DE
Hungarian (Hungary):
hu_HU
Japanese (Japan):
ja_JP
Swedish (Sweden):
sv_SE
Administrators are advised to review the Elasticsearch connector configuration and remove any customized field mappings and settings added previously for the above locales from the Override Type Mappings and the Additional Index Settings as now they are provided by the platform out-of-the-box. (Requires a Full or Concurrent Reindex!)
The Database Upgrade Report is now enabled by default and offers expanded information compared to previous releases.
After running a database upgrade, check the reports/
directory for reports about what occurred in the system during the upgrade. The new upgrade_report_diagnostics
file includes further details to diagnose any possible issues.
Feature Status Change
SCIM provides a unified, RFC compliant way to keep user/group data in sync between different applications. Liferay is a service provider and enables clients to be connected. Though the defined RESTful APIs and schemas, clients can perform CRUD operations to keep resources in sync.
Feature Status Change
The vendor has deprecated OpenSSO/OpenAM, so there is no reason for us to keep it. The alternative, which is PingAM can be integrated using our existing OpenID connector or SAML Authentication.
Feature Status Change
Segments that are just static groups of users
Feature Status Change
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.
Feature Status Change
Users can easily configure the friendly URLs for the different asset types, updating URL separators. In addition to that, they are able to select and reorder categories within a blog’s friendly URL so the users can easily identify by the URL what is the main topic of the page they are visiting.
Semantic Search now supports the Documents and Media type. Text embedding generation can be enabled via the provider configuration. Please note that the provider configuration is now located under the Global Menu: |
The upcoming Marketplace release of the Liferay Connector to OpenSearch 2.x will provide an alternative to Elasticsearch for Self-Hosted Liferay deployments.
IMPORTANT: Please note that the Liferay Enterprise Search Learning to Rank, Cross-Cluster Replication, and Monitoring applications are not compatible, and thus not supported with OpenSearch.
Here we added the capability to expose ERC and Scope for Attachments added to Object Entries. We plan to use this during Moving Object entries between environments. |
We added the permissions assigned to Custom and Modifiable Object Entries to the Objects Entries APIs' nested fields. This will be useful when we export/import Object Entries with permissions through Batch.
This new feature allows users to configure Collection Providers based on Liferay System Objects, such as Users and Accounts. |