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 GA35:

docker run -it -p 8080:8080 liferay/portal:7.4.3.35-ga35

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 GA35 and Liferay Commerce 4.0 GA35 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-ga35

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

Features

Objects

Relationship - Filtering using a parameter

Looking to provide a solution for objects that have a dependency on another object, developed by the DXP Latam team a feature to empower the power users to filter data, through the relationship.

This feature provides for users to relate data and see just the necessary information, allowing the user to not see private/unnecessary information.

https://issues.liferay.com/browse/LPS-155537​​​​​​​


Object creation


Account relationship creation


Postal Address relationship creation

​​​​​​​
Object entry

Staging

Customer can choose whether or not to publish content via display portlets since we released LPS-131578 and now we made the configuration as default
 

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.

There is a new configuration under System Settings → Platform → Infrastructure → Staging:
Publish Displayed Content by Default.

Until now this feature is enabled by default. Admins have the option to disable it.
This story boosts the performance, end users can expect faster Staging publish processes, especially in case of large Sites with lots of display portlets.

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

https://issues.liferay.com/browse/LPS-149374​​​​​​​

Core Upgrades

Improvements in upgrade log/report

There is a new feature that allows to easily identify the upgrade related log lines.

This feature relies in the log4j thread context characteristic to tag the upgrade related log lines with some thread context information.

To enable this feature you need to set the upgrade.log.context.enabled portal property to true. Default value is false. It is also needed to add the %X tag to the layout pattern template of the desired appender. This can be done by means of the portal-log4j-ext.xml file

In addition, information included in upgrade report has been improved by adding the total upgrade time to the report that is generated by the database upgrade tool when the upgrade.report.enabled portal property is set to true.
​​​​​​​
https://issues.liferay.com/browse/LPS-155537​​​​​​​

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 GA35 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 GA35 and Liferay Commerce 4.0 GA35 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

• Fixes

• List of known issues​​​​​​​