Blogs

Blogs

Liferay Portal 7.4 GA17 and Liferay Commerce 4.0 GA17 Release

We are pleased to announce the release of Liferay Portal 7.4 GA17 and Liferay Commerce 4.0 GA17!

Caption

Download options

Liferay Portal and Liferay Commerce share the same Bundle and Docker image.  To get started using either Liferay Portal or Liferay Commerce, choose the best download option suited for your environment below.

Docker image

To use Liferay Portal 7.4 GA17:

docker run -it -p 8080:8080 liferay/portal:7.4.3.17-ga17

For more information on using the official Liferay docker image see the liferay/portal repo on Docker Hub.

Bundles and other download options

If you are used to binary releases, you can find the Liferay Portal 7.4 GA17 and Liferay Commerce 4.0 GA17 release on the download page.  If you need additional files (for example, the source code, or dependency libraries), visit the release page.

Dependency Management

For development using the Liferay Platform, update Liferay Workspace to use the  latest dependencies, by adding the following line to the build.gradle file:

dependencies {
	compileOnly group: "com.liferay.portal", name: "release.portal.api"
}

All portal dependencies are now defined with a single declaration. When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.  

By setting a product info key property it will be possible to update all dependencies to a new version by updating the liferay.workspace.product property in the liferay workspace projects gradle.property file:

liferay.workspace.product = portal-7.4-ga17

When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.

Features

Objects

Managing metadata in my custom view

Now Objects Admins are able to add metadata, also known as auditable fields, in custom views in order to customize how their entries will be displayed in a table. The available fields are ID, Author, Creation Date, Modified Date, and Workflow Status.

https://issues.liferay.com/browse/LPS-143190

Managing my object’s modeling permissions and picklists individually

Now Objects users are able to define permissions both at object admin level and picklists level individually, using the Liferay Permissions Framework.

https://issues.liferay.com/browse/LPS-146758

https://issues.liferay.com/browse/LPS-146759

Allow Users to Create Templates for Objects

Now Objects users are able to create Information Templates for Objects and apply those templates while creating experiences in the page builder.

https://issues.liferay.com/browse/LPS-148544

Search

Upgraded Elasticsearch integration to 7.17

The minimum compatible version of Elasticsearch is 7.17 starting with 7.4 CE GA17 / DXP 7.4 U17. Deployments are required to update their Elasticsearch cluster to use 7.17. Please refer to the Search Engine Compatibility Matrix for details. The portal will fail on startup if the Elasticsearch server does not meet the minimum version requirement (LPS-149316).

The followings been updated:

  • Client libraries and required dependencies to 7.17.1

  • Sidecar Elasticsearch version to 7.17.0

  • Connector implementation to align with the new APIs/libraries

https://issues.liferay.com/browse/LPS-145631

Staging

Option for Instance Administrator to be able to choose whether or not to publish content via display portlets

When Staging is used with the default settings, there is no need for the widgets to publish the displayed content. In a typical scenario, admins publish to Live frequently, therefore only a few, newly created content has to be moved between Staging and Live. However, display widgets still publish the content each time, which is in most of the cases slows down the process unnecessary.
The following widgets were modified: Dynamic Data Lists Display, Form, Web Content Display and Wiki Display.

Instead of exporting/importing the content over and over again, only a reference is created during the export process. This reference is enough to build the primary key map for the staging and live ids, which is necessary to update the portlet preferences.
This feature is only applied in case of Site publication, portlet publication is not affected.

https://issues.liferay.com/browse/LPS-131578

User & System Management

Language Key management for business users

Now, the business user will be able to perform actions using the Language Key management UI.

  • Import and export language key translations

  • Know which languages a Language Key translation has been overridden in.

  • See if a Language Key has translation overrides in my currently selected Language

  • Find Language Keys overridden in a specific language

https://issues.liferay.com/browse/LPS-145850

Documentation

All documentation for Liferay Portal and Liferay Commerce can now be found on our documentation site: learn.liferay.com.  For more information on upgrading to Liferay Portal 7.4 GA17 see refer to the Upgrade Overview.

Compatibility Matrix

Liferay's general policy is to test Liferay Portal and Liferay Commerce  against newer major releases of operating systems, open source app servers, browsers, and open source databases (we regularly update the bundled upstream libraries to fix bugs or take advantage of new features in the open source we depend on). 

Liferay Portal 7.4 GA17 and Liferay Commerce 4.0 GA17 were tested extensively for use with the following Application/Database Servers: 

Application Server

  • Tomcat 9.0

  • Wildfly 18.0, 23.0

Database

  • MySQL 5.7, 8.0

  • MariaDB 10.2, 10.4

  • PostgreSQL 12.x, 13.x

JDK

  • IBM J9 JDK 8

  • Oracle JDK 8

  • Oracle JDK 11

  • All Java Technical Compatibility Kit (TCK) compliant builds of Java 11 and Java 8

Search Engine Compatibility Matrix

Source Code

Source is available as a zip archive on the release page, or on its home on GitHub. If you're interested in contributing, take a look at our contribution page.

Bug Reporting

If you believe you have encountered a bug in the new release you can report your issue by following the bug reporting instructions.

Getting Support

Support is provided by our awesome community. Please visit helping a developer page for more details on how you can receive support.

Fixes and Known Issues