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.