Release Notes
This new feature introduces a composable, fragment-based way to build and customize the account selector experience.
It enables developers and business users to assemble panels, buttons, and account/order views without hardcoded dependencies.
The main orchestrator fragment manages navigation, dropdown behavior, and interactions across configurable panels, delivering greater flexibility, improved user experience, and fine-grained control directly from page building.
With Liferay's New Headless Content Management System (CMS), creating, organizing, and publishing content is simpler because all content management tasks are brought together in a single interface. Your content is independent of its presentation, allowing you to reuse it across sites, pages, and APIs. You can work with articles, documents, media, and more, while taking advantage of features like global asset views, organized spaces, and cross-site publishing. Thanks to Liferay Objects, the CMS provides flexible content structures and ensures a smooth, consistent authoring and publishing experience. Key Benefits:
|
To prepare for Microsoft’s removal of Azure Access Control Service (ACS) for SharePoint in Microsoft 365 starting April 2, 2026, we’ve evolved the SharePoint connector authentication model. This ensures customers can continue accessing SharePoint seamlessly after April 2026, without disruption.
Key Benefit:
Ensures uninterrupted access to SharePoint after ACS deprecation
Aligns with Microsoft’s supported and future-proof authentication standards
Improves long-term security and compliance
The permissions-check modal introduced during content publishing is now optional. While this feature provides additional control by allowing users to review permissions before publishing, we recognize that it may add unnecessary steps for some workflows. Customers can now publish in just one step without having to check the permissions first.
Key Benefits:
Greater flexibility to adapt publishing workflows
Maintains enhanced permission control where needed
Avoids unnecessary steps for existing or streamlined flows
Respects different customer contexts and usage patterns