With this new feature, Instance Administrator can export audit data filtered by user as well as filtered by site. They can also store site data for audit events.
Release Notes
We display some additional messages to Site and Site template Administrators when there is a Friendly URL collision between Site page and Site template page.
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.
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.
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.
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.
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.
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.