Two new permissions were added to View and Edit the channel default tab in the Account Management Pages. Users are now able to activate/inactivate the tab.
Release Notes
The allowable size of an Account Name has been increased to 250 characters in line with industry standards.
Enables the ability to add new remote shipping calculations via client extension.
Ability to add new steps to the checkout process via client extension.
Default View and Download permissions for documents have been adjusted to match the behavior prior to the changes introduced in LPD-16744, restoring the expected user experience.
Highlights:
The View and Download permissions will be linked by default when uploading documents through the single and multiple file uploaders
The Permissions configuration UI is improved so users can more easily recognize that the View and Download permissions are separate permissions
The Download permission is now automatically included when a user shares a document and assigns permissions
Liferay Labs is an innovation hub within Liferay Marketplace dedicated to exploring newer technologies and developing experimental features. It provides a wide range of useful applications developed by Liferay staff. These are available to the community from Marketplace.
Liferay Labs serves as a platform for rapid prototyping and testing new ideas. These apps may often be integrated as future Liferay features. Under Liferay Labs, you can also find all the legacy apps that are no longer under official support.
All apps offered by Liferay Labs are free but without support. However, you may give feedback on apps containing beta features as it helps in improving them for a future release.
Key benefits:
1. Innovation Hub: serves as a testing ground for new and experimental technologies within the Liferay ecosystem.
Enables rapid prototyping and exploration of novel ideas.
2. Community Access: provides a platform for sharing valuable applications developed by Liferay staff with the broader Liferay community.
Makes these applications readily available through the Liferay Marketplace.
3. Future Feature Roadmap:Acts as a proving ground for potential future features of the Liferay platform. Allows for real-world testing and user feedback on new functionalities before official integration.
4. Legacy Application Repository: serves as an archive for legacy applications that are no longer officially supported. Enables users to access and utilize these applications if needed, while acknowledging their limited support.
This functionality refers to segments that are static groups of users.
That said, users can now utilize either user group-based segments or dynamic segments instead of static ones moving forward.
This functionality refers to tracking events related to non-default asset types and visualizing the data on a dashboard. From now on, customers will no longer be able to use this specific method to track views of non-default asset types and visualize this data on a dashboard in Analytics Cloud
Using custom event tracking is the recommended way to track your custom assets from now on.
This improvement allows users to customise the appearance of their Liferay instance more effectively with new properties in the .yaml
file for Theme CSS and CSS Client Extensions.
Key benefits:
Admins can personalise the interface for both the admin panel and the entire platform.
A more cohesive, branded appearance will improve usability and satisfaction for all users.
Allows fine-grained control over where customisations are applied.
Liferay 7.4 introduces the ability to manage language translations directly within client extensions. This enhancement allows developers to provide multilingual support for custom labels and properties without relying solely on OSGi bundles.
Key benefits:
Developers can now define and manage language keys and translations within the client extension itself, ensuring that all labels and custom properties are displayed correctly across different languages.
This feature eliminates the issue of untranslated labels with dashes, providing a consistent and professional appearance on multilingual sites.
Simplifies the process of adding translations, reducing the need for manual intervention and external OSGi bundles, thus accelerating the development and deployment of multilingual features.
Empowers developers to create more flexible and fully localized custom elements and themes, enhancing the overall versatility of the Liferay platform.
The addition of new translations and locales ensures that users in regions like Macedonia, Norway, Belgium, Switzerland, and Austria can interact with the platform in their preferred language or regional variation.
Key benefits:
Tailors the user experience for specific markets and regions, improving relevance and usability.
We made the platform more inclusive by expanding language and locale options.
We continue to improve the API Builder by adding new endpoints: GET single element. With the GET single element new endpoint, we allow users to create a GET endpoint that only retrieves a single element using a path parameter.
One particular thing is that users can select as a path parameter any unique custom field defined in the object apart from ID and External Reference Code.
New POST endpoint inside API Builder to add the possibility not only of recovering information of the entries but also of creating them.
As in the GET methods, users can define the schema to use for the request and the response. Both can be the same or two different ones. And can even be one already used previously on another endpoint definition.
Company and Site scope is available too.
The POST method only works for creating new entries of the main object . No entries for the related objects can be created yet at the same time.
We have introduced a configuration feature within the Asset Library, enabling users to decide whether a Vocabulary created there is solely required at the Asset Library level or if it extends to the connected Sites as well.
We have introduced case-sensitive tagging for page creators, allowing tags to be saved and displayed exactly as created, whether in uppercase or lowercase. The feature ensures case sensitivity for tag creation, case-insensitive searching, and autocomplete, while maintaining backward compatibility for existing tags.
Users now have the ability to restrict channel access to certain Accounts via the eligibility tab on the channel admin pages. The ability to restrict certain Account Addresses to be used on certain channels has also been added. This is managed via an Eligibility tab on the address that allows the user set channel usage.
Introducing new key improvements to the B2B Guest Checkout experience, enhancing the overall user journey and providing greater flexibility for both new and returning customers.
Guests now have the option to sign in or sign up during the checkout process, directly from the mini-cart. Once logged in, users can either select an existing account or create a new one, ensuring that they can move through the purchase flow smoothly without disruptions. Upon setting the account, guests, now logged-in users, will be redirected to the checkout, making the transition to completing the purchase seamless.
Additionally, if a guest decides to sign in without necessarily checking out, the guest cart will now be merged with their account after logging in. This ensures that any items added to the cart during the guest session are retained when they sign in or select an existing account, improving the continuity and experience for returning users.
Key benefits:
1. Enhanced User Experience: By allowing guests to sign in or create an account directly from the mini-cart, we provide a more intuitive and streamlined checkout process. Guests can complete their purchase with minimal steps, reducing friction and abandonment rates.
2. Cart Persistence: The ability to merge guest carts ensures that items are not lost when guests decide to sign in or register. This improves convenience for returning users and supports a smoother transition between sessions.
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 and determine how the categories will be presented in the friendly URL along with the title.
Users are able to set different values for the asset types separators in the friendly URLs. Also, they are able to reset to default value, so for those asset types that they have clicked on this option, the separator will be the value defined by default for those specific asset types.
This set of improvements aims to simplify the manual work users must do to resolve conflicts when publishing a publication. Now, instead of raising a conflict to be resolved manually by the user, the system will try to overwrite conflicting changes in production with the modifications done in the publication, meaning that the Modification and Modification deletion conflict types won’t be presented for the user anymore.
In the case of a Deletion modification conflict, the system won’t resolve it automatically, but now it makes it easier to keep the modifications made in the publication. In the Conflicting changes screen, we added a button with the option to "Restore in Production" for conflicts in which the asset was deleted from production and is now in the Recycle bin.
Key benefits:
Reduce the amount of manual work by automatically solving most of the conflicts.
Improve user satisfaction and reliability on publications by ensuring that assets supported by Recycle Bin can be quickly restored, avoiding requiring the user to discard needed changes.
In order to make it easier to manage and override portal language translations, modules have a new configuration that allows language keys to be defined specifically for a single module. This also allows the user to override a system-wide language key programmatically within the module. An existing feature allows modules to use the Language Resources header ( A new variable was added within this header, |
Official release of Liferay Data Sets, moving from Beta to Release! Data Sets are a powerful and flexible way to retrieve, manage, visualize, and interact with structured data in Liferay DXP. Built on top of Objects and leveraging Liferay’s robust ecosystem, Data Sets exemplify the “build Liferay with Liferay” philosophy. With seamless integration with compatible Headless APIs, administrators can easily configure Data Sets and empower end-users with a rich, customizable experience for consuming and interacting with data.
Key benefits:
Retrieve Data: Fetch information from any compatible Headless API to use as a Data Set source.
Manage Flexibility: Administrators can customize what parts of the API response are included, along with filters, sorting options, and available actions.
Visualize Data: Multiple visualization options make it easier than ever for end-users to consume data meaningfully.
Enable Interaction: End-users can interact dynamically with data using the filters, actions, and tools configured by administrator
Allow users to move web content and document structures between environments
Key benefit:
Addresses a feature gap when moving web content and documents between environments
With this development, the publication of Knowledge Base articles will be schedulable, in particular, the feature is so designed:
The primary Publish button will have an arrow down with the “Publish” option, that will immediately publish the article, and the “Schedule” one.
Clicking the Schedule option, will make a modal appear so the user can set a date and time for the article to be published.
The Scheduled article will have the SCHEDULED status that will change to APPROVED on the scheduled date
A tooltip with the scheduled date information will appear when hovering the
question-circle-full
icon placed next to the SCHEDULED state.
Editing a scheduled article will provide the user the ability, by clicking the primary button that has turned into “Scheduled”, to:
Cancel the operation
Publish Now
Schedule: this option will save the article, date & time changes and the user will return to the previous screen before entering edit mode
Additional feature: A Knowledge Base article deletion action will move it to the Recycle Bin so that it can be restored.
Now user are able to:
Configuration of document size for copying in D&M
Bulk copying of documents and folders
Currently the copy action for documents and folders is able to be performed in Portal without fully respecting the site-asset library relationship. The expected behavior is:
An asset library must be connected to a site in order to copy a document over to the site
A document cannot be copied from a site to an asset library (only the other way around)
We can enforce a stricter check when performing the copy action between asset libraries and sites. Instead of the end user receiving a success message when copying a document to a disconnected site, an error message should appear telling the user to set the connection first.
Document Types contained in a document are being copied in Documents and Media so that they can be easily reused.
Categories and Tags in Documents and Media are being automatically copied so they can be easily reused on a new site.
Users are now able to properly search in the portal using the Search widget (in applications that have data restricted by account).
This feature allows you to leverage the functions of Liferay’s caching framework. Our current measurements indicate about 10%/30% performance increase in database writing operations, also 10 times faster reading performance!
To reduce the maintenance costs of providing a full document’s preview, the following changes are being introduced:
“No preview available” state when the file size exceeds the preview size limit.
Merge “File Entries” and “PDF Preview” settings under “File Preview Limits”
Rename "File Size Limits" to "File Upload Limits" with a reviewed and more understandable Description copy
The user is being informed that the generated preview may not correspond to the entire document
This development introduces the ability for the user to set the file size at asset library’s level. This settings will override the already existing one at System level when the latter is bigger. As a general rule, when both are set the lowest applies.
Users can add validations to verify field values that, when used in combination, are unique.
Limitation: numeric fields such as Integer, Long Integer, Decimal, Precision Decimal will be stored as null.
The user experience of the Management Toolbar present in multiple applications (Web Content, Blogs, Documents & Media) has been improved:
- Separate sections for filter and order.
- Changed “+” with “New” for clarity.
- Moved info icon to the right.
Validate relationships to prevent duplicate names in child objects.