As part of Liferay strategy to increase product led growth, we are going to offer a free tier version of our CMS with some key limitations to allow users to test and interact with the product enough to understand if the product meets their needs.

To make this possible, we need to implement how the tiers (Free and Enterprise) will affect the product and how these customers can move from the Free to the Enterprise through the product.

Key Benefits:

• Lower Barrier to Entry: Users can start building and testing their ideas immediately without upfront investment, making it easier to validate the CMS for their specific needs.

The product currently relies on a legacy CMS alongside a newly developed CMS, requiring parallel maintenance, duplicated functionality, and fragmented content workflows. This increases operational cost, slows down feature delivery, and creates inconsistencies in how content is managed and consumed.

This epic aims to inform the users that we are putting the current CMS in maintainance mode, preparing the field to add the feature flag in next releases

Key Benefits:

• Inform the users about the features set as In Maintenance

During the reviewing of the CMS experience and fixing bugs, we detected some product gaps and improvements that can make the user experience smoother, so this epic’s goal is to tackle them to ensure a stable and reliable user experience.

Key Benefits:

• Allow to search members in a space for non admin users

• Improved category creation

• Filter by space for content structures

• List view for Space home view

We have introduced several new bulk actions to the CMS to help you manage large volumes of content more efficiently. Instead of handling items individually, you can now perform complex administrative tasks across multiple selections simultaneously.

Key Benefits:

• Assign Workflow for Content Structures in bulk

• Expire content in bulk

• Delete versions of a content in bulk

• Export translations of different content in bulk

As part of improving asset management efficiency, this epic introduces bulk Copy and Move actions for assets within the CMS. These actions will allow content creators to organize and duplicate multiple assets at once, across locations in Spaces they have access to. The functionality should maintain the same user experience principles and behavior as the existing single-asset Copy and Move actions, extended to handle multiple selections simultaneously.

Key Benefits:

• Copy assets in bulk

• >Move assets in bulk

The Questions Widget is a legacy application that was primarily maintained to support Liferay Ask. With the recent migration from Ask to Discuss (Liferay's new forum platform), this widget is no longer needed. Therefore, the Questions Widget is being deprecated to reduce technical debt and ongoing maintenance costs.

Search re-indexing has been optimized to deliver shorter re-index windows, especially for Objects-heavy deployments. In testing against production databases and architecture, we observed re-index improvements of 2x or more across the evaluated datasets, with gains reaching up to 10x on specific workloads. The optimizations primarily targeted improvements that scale with the volume and complexity of Object data being indexed.

Key Benefits:

• Shorter re-index windows reduce maintenance overhead and downtime risk

• Validated on a production-equivalent distributed architecture

• Largest impact for Objects-heavy installations

Building on the automated database repair routines introduced in 2025.Q4, Liferay DXP continues to expand the set of repair processes that run during the upgrade. Based on additional research into customer upgrade issues, new repair routines automatically identify and correct further sources of database inconsistencies, orphan references, and invalid data — before they cause upgrade failures or performance bottlenecks. These repair routines remain targeted at known issues with data structures only, keeping your critical data content safe. Details of each repair process continue to be provided for review in the Upgrade Report after the database upgrade completes.

Key Benefits:

• Minimize risks for current and future upgrades

• Automates data maintenance

When using the Liferay DXP Database Partitioning feature, the system now enforces strict access controls ensuring only the authorized database partition is accessible for any given request. This completes foundational security work and extends proper enforcement to all Liferay entry points, including Headless APIs and Client Extensions.

Key Benefits:

• Prevents unauthorized cross-partition data access in multi-tenant environments

• Ensures consistent partition access enforcement across all Liferay entry points (Headless, Client Extensions)

This is a major version release that brings important platform updates and security enhancements alongside several necessary breaking changes to ensure the continued delivery and stability of Liferay Developer Studio.

Key Benefits:

• Eclipse Platform Update: The underlying platform was updated to Eclipse 2025.12, taking advantage of the latest features and security updates from Eclipse. For more information, please see https://eclipse.dev/eclipse/news/4.38/.

• Blade Version Update: The packaged Blade version was updated to 8.0.1-SNAPSHOT.

This feature introduces a centralized administration interface within the Data Set Manager to oversee and moderate User Views. Administrators can now access a global list of all User Views to monitor usage or perform cleanups.

Key Benefits:

• Centralized Oversight: A new "Manage User Views" button in the Data Set Manager provides a complete list of all User Views for easier monitoring.

• Contextual Access: Admins can jump to the management view from specific Data Set settings, where the list is automatically pre-filtered to show only the views belonging to that Data Set.

• Administrative Control: Enables admins to maintain system hygiene by deleting individual or multiple User Views via bulk actions.

• Full Visibility: Provides key details at a glance, such as which user created the view and which Data Set it belongs to, ensuring better governance of user-generated configurations.

From now on CK Editor 5 will be the default rich text editor present in Liferay DXP. For those customers with custom plugins or other particularities over CK Editor 4 that don’t want to upgrade yet, they can enable the deprecation Feature Flag (FF-11235) to have CK Editor 4 as default in DXP.

Note: CK Editor 4 still remains the default editor on some of the DXP features, those which are in Maintenance Mode such as Knowledge Base or Blogs, these experiences will not be migrated to CK Editor 5.

From now on CK Editor 5 will be the default rich text editor present in Liferay DXP.

Note: CK Editor 4 still remains the default editor on some of the DXP features, those which are in Maintenance Mode such as Knowledge Base or Blogs, these experiences will not be migrated to CK Editor 5.

Content teams can now find and replace text, URLs, or terms across the entire CMS repository in a single action — covering titles, content fields, and friendly URLs. Every operation includes a mandatory preview, scoped targeting, and automatic versioning, so large-scale updates like rebrandings or URL migrations are fast, reversible, and low-risk.

Key Benefits:

• Cut rebrandings and terminology rollouts from hours of manual edits to a single bulk action.

• Preview every change before it's committed, with automatic versioning if you need to roll back.

• Scope replacements by site, content type, or field so global updates stay surgical instead of sweeping

CMS administrators can now modify content structures and their repeatable fields after publication — adjusting field configurations, nesting order, and repeatable settings without deleting existing content. Teams iterate on their data models as business needs shift, and all previously published entries stay intact.

Key Benefits:

• Refine your content model based on real-world usage instead of locking in every decision up front.

• Skip the "delete everything and rebuild" cycle when requirements change — existing entries come along for the ride.

• CMS admins adjust structures directly, without pulling in developers or database work for every tweak.

Data modelers can now define Link Content fields that let content creators select existing entries from other objects—single or multiple—instead of retyping the same values across entries. The CMS moves from isolated documents to a connected data model, so information like vendor names, categories, or authors stays consistent across every publication.

Key Benefits:

• Eliminate typos and inconsistencies by picking existing entries instead of re-entering text.

• Reuse the same author, category, or vendor across hundreds of entries—update it once and it propagates everywhere.

• Support both single and multi-select relationships, from "one author per article" to "many products per campaign.”

This release rounds out the Pages Management APIs with new endpoints, broader page-type coverage, and refinements to how references and scopes are handled. The updates close long-standing gaps — supporting more page types end-to-end, expanding the catalog of page elements and fragments exposed through the API, and hardening the data architecture around scopes and secure references. The result is more reliable imports, exports, and staging across every site component.

Key Benefits:

• Broader API coverage: every page type is now supported end-to-end, not just the subset covered before.

• Fewer surprises in staging: scope-aware identifiers catch missing references and deleted assets before they break the live site.

• Consistent behavior across sites, staged environments, and imported content — the API no longer behaves differently depending on the page type.

We've refined how users discover and install Marketplace fragments from inside the Page Builder. Browsing, previewing, and installing partner and community fragments now feel native to the editing flow—fewer clicks, clearer discovery, and less context switching between the editor and the Marketplace. Native, already-installed, and Marketplace-available fragments now live side by side in the same experience.

Key Benefits:

• Faster discovery and installation of Marketplace fragments without breaking the editing flow.

• Clearer distinction between native, installed, and Marketplace-available fragments, so builders pick the right one at a glance.

• Less context-switching: everything happens inside the Page Builder instead of jumping to the Marketplace and back.

The Style Book Editor has been improved to make managing design tokens simpler and more intuitive, with a clearer approach to editing colours and improved overall usability.

Key Benefits:

• Faster updates: Edit colour tokens quickly through a single, clear interaction point.

• Easier to use: Fewer competing controls reduce confusion and make the editor more approachable.

• Consistent experience: Interaction patterns now align with the Page Editor, improving learnability.

• Built for growth: A stronger foundation to support future design token capabilities and enhancements.

• Fewer errors: Improved interactions reduce friction and mistakes when updating styles.

Style Book tokens are now aligned with Clay variables, ensuring that design changes apply consistently across UI components and themes.

Key Benefits:

• Reliable theming: Changes made in Style Books now correctly reflect across all Clay-based components.

• Real consistency: No more gaps where updating a token doesn’t affect parts of the UI (e.g. alerts, buttons).

• Better visibility: Token changes are accurately represented in the Style Book editor.

• Stronger foundation: Clay now exposes core variables (colours, typography, spacing) as CSS custom properties, making them easier to control.

• Future-ready: Sets the groundwork for more advanced theming and design system capabilities.

The Global Menu has been promoted from Beta to GA and is now the default, fully supported navigation experience in Liferay DXP. It provides a single, consistent entry point to access applications and settings, with improved structure, stable behaviour, and integrated search for faster navigation.

We are excited to announce the General Availability (GA) of the OpenSearch 2 Connector v2.0.0 for 2026.Q1 and v2.1.0 for 2026.Q2. This release is an important milestone in our Cloud Native Experience strategy, providing a viable alternative for Liferay DXP users.

This version has undergone additional testing and validation to ensure dependency alignment with the latest OpenSearch 2 clients and field mapping consistency with our Elasticsearch 8 connector.

The new version of the application is will be released on Liferay Marketplace.

Key Benefits:

• Native AWS Integration & Cost Optimization: Connect Liferay DXP with AWS OpenSearch Service. By leveraging managed infrastructure, organizations can reduce operational overhead, streamline their cloud stack, and optimize hosting costs through AWS-native service configurations.
• Flexible Search Architecture Production-ready alternative to Elasticsearch. This connector ensures that Liferay DXP remains flexible, allowing you to choose the search engine that best aligns with your infrastructure requirements and corporate standards.

Note: Liferay supports the connector and its features. While Liferay can provide an example deployment configurations for AWS OpenSearch Service, the management and maintenance of the underlying service remain the responsibility of the infrastructure provider.

Manage site updates with total confidence using the new Maintenance Mode. This feature allows Site Administrators to take a site offline for the public while maintaining full operational access behind the scenes. When enabled, visitors receive a dedicated maintenance page with the correct SEO-friendly status (HTTP 503), while administrators can continue to navigate, edit, and verify site pages to ensure everything is perfect before going live again.

Key Benefits:

• Safe Production Verification: Unlike standard deactivation, Maintenance Mode allows admins to view and test the full site experience live, ensuring that deployments are successful before the public ever sees them.

• SEO Protection: By serving a proper 503 Service Unavailable status, the system tells search engines that the downtime is temporary, protecting your search rankings during major updates or migrations.

Managing large-scale site deployments just got easier. We have introduced new headless API endpoints that allow developers to toggle site states (Active or Inactive) programmatically, bypassing the need for manual configuration within the Control Panel.

Key Benefits:

• Automated Site Governance: Enables high-speed bulk management of site states, allowing your team to sync site availability with external business systems or custom orchestration tools.

• Enhanced System Stability: Built-in safeguards protect the platform by preventing the accidental deactivation of essential system sites (like Global), while strict permission validation ensures only authorized users can trigger state changes.

Reviewing complex page updates is now faster and more intuitive. We’ve introduced a Review Side Panel within the Publications Review Change screen that automatically surfaces content changes made on a Content Page. Instead of manually digging through the full change list or a Pages’ Children tab, reviewers can now see exactly which text and images have been modified in a page’s Fragment Entry Links via a consolidated, easy-to-read list.

Key Benefits:

• Focused Decision-Making: Instantly identify high-impact changes (like text and image updates) without getting lost in technical changes.

• Streamlined Workflow: Eliminates the need to cross-reference multiple tabs or Fragment Entry Links, allowing content reviewers to complete reviews with total confidence.

The page reviewing experience now provides a more accurate way to locate and compare changes. The Publications Display tab for Content Pages now provides the Unified view, highlighting additions, removals, and format changes, so you no longer have to hunt for differences on the new page version.

Key Benefits:

• Review accuracy: Reviewers feel confident that no change goes to production without the proper attention.

The AI Assistant is a versatile and powerful tool designed specifically for content creators to enhance their productivity and streamline workflows. By centralizing AI-driven content creation into a single, easy-to-use application, the AI Assistant simplifies the process of generating and managing diverse types of content. Whether you're working on blogs, Knowledge Base articles, or page layouts, the AI Assistant offers the tools and flexibility to help you work smarter and faster—all in one place.

Availability: The AI Assistant is a cloud-based application readily accessible on the Marketplace, making it easy to integrate into your existing digital ecosystem. Its cloud infrastructure ensures reliable performance and scalability, providing users with consistent and seamless access to its capabilities.

Due to the upcoming migration to Jakarta EE, we are deprecating all the current versions of our application servers to prepare for the release of the new versions that are Jakarta EE 10 compatible. This is a breaking change and so new app server versions will replace the old versions.

Deprecated:
Apache Tomcat 9
Wildfly 26.1
Jboss EAP 7.4
Weblogic 14

In 2025.Q3 we are adding support for the following application servers:
Apache Tomcat 10.1
Wildfly 30
Jboss EAP 8.0
Weblogic 15 (Pending release from Oracle)

When filtering a set of items on a Data Set, sometimes we will be interested in filtering for a field that is part of a relationship.
With this new capability, we enable users to choose to filter by children of complex objects.

The Centralized Products Eligibility and Configuration Management feature empowers catalog managers to efficiently manage individual products through multiple configuration pages containing all catalog’s products. With tools for manual configuration, eligibility-based visibility, and some bulk editing, this feature ensures streamlined operations and enhanced control over product offerings. Additionally, it enables faster and smarter management of product eligibility for channels, order types and accounts.

Key benefits:

1. Improved Catalog Management Efficiency:

• Simplified product configuration editing via a centralized, flat table view.

• Streamlined workflows for managing product attributes like visibility, minimum/maximum quantities, eligibility and much more.

• Avoid duplicating products to manage specific configurations by modifying targeted configurations instead.

• Perform batch updates on visibility, eligibility, and other product attributes for multiple products, whilst inheriting base setting from the Master catalog configuration

• Leverage pre-filled default master configurations to ensure consistency and simplify product setup when adding new products in a catalog.

2. Enhanced Control over Product Eligibility and Visibility:

• Define and manage eligibility rules tailored to specific customer groups, channels, and accounts

• Quickly adjust product availability and settings for various markets and segments (e.g. B2B vs B2C).

• Streamline the management of seasonal items or time-sensitive offerings using configuration scheduling.

This release introduces a new Multishipping feature to the storefront, allowing customers to ship parts the same order to multiple addresses with a single checkout. Whether customers are sending gifts to different recipients or shipping products to various locations, the Multishipping feature offers a seamless and flexible shopping experience.

Administrators can allow multishipping in their site through a new configuration in the site’s Channel details page. The customers can access a new “Multishipping” tab in the Open Order Details page to easily manage the Delivery Groups and customize the quantity of each order item for every Delivery Group for the order before the checkout.

Please note that this feature is available through the existing “Commerce Classic Site Initializer” Beta feature flag. To enable it, open the Applications Menu → Control Panel → Instance Settings → Feature Flags → Beta.

Key benefits:

1. Easy to Setup: Multishipping can be activated for your site by enabling “Allow Multishipping” in your site’s Channel Details page.

2. Flexible Address and Delivery Management: Customers can easily set different shipping addresses or different delivery dates for the same address in the context of the same order.

Enhance the user experience by allowing users to directly provision cloud applications from marketplace platform, simplifying application deployment.

Key benefits:

1. Streamlining Application Provisioning: Enable users to provision cloud applications directly from the Marketplace platform, eliminating the need for complex manual processes and without leaving the platform.

2. Intuitive User Interface: Provide an easy-to-use interface for installing and uninstalling cloud applications directly from the marketplace, including an intuitive form for inputting necessary information.

3. Efficient License Management: Offer a clear and intuitive interface for managing application licenses, ensuring compliance and optimizing resource utilization.

This feature allows warehouse managers to define granular eligibility rules for accounts and account groups to access specific warehouses. This enables fine-grained control over which customers can see and purchase inventory from which warehouses.

Key benefits:

1. Improved Inventory Management:

• Prevent unauthorized access to inventory data.

• Strategically control product visibility based on inventory quantities and stock levels.

• Optimize inventory allocation across customer segments.

2. Enhanced Customer Experience:

• Provide a more relevant and personalized shopping experience.

• Improve customer satisfaction by prioritizing access for key customer segments.

3. Increased Revenue:

• Generate higher revenue from valuable customer segments by prioritizing their access to inventory.

4. Reduced Lost Sales:

• Minimize lost sales due to stockouts by limiting product visibility for certain customer groups.

Added External Reference Codes for references in widget configurations in Commerce and User Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.

Key benefits:

References within the following page widgets now use External Reference Codes instead of internal IDs:

• Cart

• Cart Summary

• Category Content

• Commerce Addresses

• Commerce Category Navigation

• Mini Cart

• Open Carts

• Option Facet

• Order Forecasts Chart

• Organization Management

• Placed Orders

• Product Comparison Bar

• Product Comparison Table

• Product Details

• Product Downloads

• Product Publisher

• Search Results(Commerce)

• Specification Facet

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.

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.

External Reference Code is now supported in Currencies.

It is also now possible to use the ERC to update and delete Currencies via their headless APIs.

Additional ERC support for the entities that have a relation with a currency has been added when creating new Catalogs, Channels, Price Lists/Promotions, Orders and Payments.

Key benefits:

• Enhanced Data Management;

• Improved Integration Capabilities;

• Enhanced System Scalability;

• Reduced Errors

This feature enhances the filtering capabilities within the headless-admin-user endpoints by enabling filtering based on custom fields for Accounts and Account Groups.

Key benefits:

• Improved Data Retrieval Efficiency

• Enhanced Data Management

• Increased User Productivity

This feature focuses on rigorously aligning the User Management headless APIs with the established standards and best practices. This includes:

• Comprehensive Functionality Testing: Verifying that all API endpoints (PATCH/POST/PUT) correctly update the expected fields in user records.

• Custom Field Support: Ensuring seamless integration and proper functioning of custom fields within the API interactions.

• Error Handling: Thoroughly testing error handling mechanisms and verifying that informative and user-friendly error messages are returned in all relevant scenarios.

• Data Manipulation Capabilities: Confirming the correct and efficient functioning of sorting, filtering, and other data manipulation operations within the API.

Key benefits:

• Enhanced User Experience: By ensuring the reliability and accuracy of the User Management headless APIs, we provide a seamless and efficient user experience for developers and integrators.

• Increased Developer Productivity: Well-defined and documented APIs empower developers to build integrations quickly and confidently, reducing development time and effort.

• Improved System Stability: Rigorous testing and alignment with standards minimize the risk of unexpected errors and system disruptions, leading to a more stable and reliable user management system.

• Enhanced Data Integrity: By ensuring accurate data updates and consistent API behavior, we maintain the integrity and consistency of user data across the system.

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.

This feature enables users to export a CSV file containing detailed information about segment membership, including a list of all known individuals within a segment and their associated data, providing valuable insights for stakeholders.

Highlights:

• Export Capability: Allows users to generate a CSV file containing segment membership data.

• Comprehensive Details: Includes a list of all known individuals in a segment, with details such as names and email addresses.

• Actionable Insights: Equips stakeholders with valuable data for analysis and decision-making.

Users can access a new Performance tab on the Content Dashboard, which provides detailed metrics for assets, including visitor behavior and the top pages where each asset is featured. Data can be filtered by anonymous or known visitors. These metrics are available for Blogs, Documents and Media, and Web Content and are exclusively accessible to users connected to Analytics Cloud.

• 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 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.

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

We added External Reference Codes for Categories and Tags and their associated API’s, improving their portability for data migration scenarios.

Highlights: 

• Users can now perform CRUD operations using a Tag’s ERC through its headless API (Keyword)

• Users can now perform CRUD operations using a Category’s ERC through its headless API (TaxonomyCategory)

We added External Reference Codes for references in widget configurations in Content Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.

Highlights:

References within the following page widgets now use ERC’s instead of internal ID’s:

• Announcements
• Web Content Display
• Category Filters
• Questions

We added several API endpoints for Documents & Media to improve programmatic management of these entities.

Highlights:

• Users can now add, delete, and retrieve document types via headless API (DocumentDataDefinitionType)

• Users can now add, delete, and retrieve document metadata sets via headless API (DocumentMetadataSet)

It is now possible to subscribe to documents and folders, allowing users to receive notifications when they are updated.

Highlights:

• Users can now subscribe to documents and folders through the “Subscribe” action and through the Subscribe icon in the Info Panel

• If a user subscribes to a folder, all documents and subfolders within it will be automatically subscribed to as well

During the publishing process, users can both define and manage permissions, as well as schedule publication dates for their web content. When creating content for the first time, users will have the opportunity to conveniently review and manage permissions. Furthermore, when editing previously created content, users can also adjust permissions directly from the editor view. Additionally, users can easily select the desired publication date for their content during the publishing process.

• 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 release expands the support of the Timeline History feature to Blogs, Wiki pages, Bookmarks, Forms, Knowledge base, Message boards, and Categories. The feature enhances the publication toolbar with tools to detect and manage collaboration conflicts.

• A timeline icon shows recent modifications in the same asset, which may have been done in production or parallel Publications.

• The user can view, discard, or move these changes directly from the toolbar.

• Warning icons appear to make users aware of current conflicts in the Publication.

Key benefits:

• Enhanced context for content editors and managers for a streamlined collaboration.

• New capabilities to detect conflicts before publishing time, while users may have more time to decide how to resolve conflicts without the go-live pressure.

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.

Provided an option to turn the “Out-of-date” feature on/off. When turned on (the default behavior before this release), ongoing publications created in previous Liferay versions were labeled as “Out-of-date” after the upgrade and could not be modified or published. This feature is now off by default, and users can publish these publications without Liferay support.

Key benefit:

Increase manageability over publications and the ability to publish any previous modification, including after Liferay upgrades.

The two separate option menus currently displayed in the Web Content Display widget have been merged into a single, consolidated dropdown menu for content creators. This new menu will improve the user experience by reducing confusion and unnecessary clicks, ensuring all relevant widget actions (e.g., Hide Widget, Duplicate, Export/Import, etc.) are easily accessible.

Added logging to indicate the completion of fragment deployments via the deploy folder. This provides better visibility into the deployment process and allows for tracking deployment duration.

There are some advantages of including a message like that, for example:

• Count the duration of a deployment
• See the fragment progress deployment until it is deployed.

Improved keyboard navigation and column resizing for Miller columns. Users can now navigate between columns both horizontally (deeper levels) and vertically (same level) using the keyboard. Column widths are also responsive, adapting to different screen sizes.

• Boost Liferay’s platform with drag-and-drop, multi-selection, and cut/copy/paste features for easier field and fragment organization.

• Fine adjustments in the User Experience when managing page components through in bulk multiselection

The updated Clay chart colour palette improves accessibility and usability by creating more contrast and adding more variations. Now users can easily distinguish charts, icons, and field sets, reducing confusion and improving clarity.
 

Key benefits:

• Now we have more design flexibility for Liferay’s current and future products.

• Accessible and distinguishable colours that will improve and unify the platform usability and UI.