This website uses cookies to ensure you get the best experience. Learn More.
Caption
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.
To use Liferay Portal 7.4 GA75:
docker run -it -p 8080:8080 liferay/portal:7.4.3.75-ga75
If you are used to binary releases, you can find the Liferay Portal 7.4 GA75 and Liferay Commerce 4.0 GA75 release on the download page. If you need additional files (for example, the source code, or dependency libraries), visit the release page.
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-ga75
When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.
The instance administrator can create the email templates including the first name.
https://issues.liferay.com/browse/LPS-176074
The batch engine API allows developers to export/import data, but it requires developers to provide a configuration with multiple parameters. With the new auto-generated endpoints, it is easier to perform export operations in the portal. The export endpoints is asynchronous, so it will provide a taskId in order to retrieve/download the records requested. The endpoints follow this format:
https://issues.liferay.com/browse/LPS-170619
Template propagations are run completely in the background. 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.
https://issues.liferay.com/browse/LPS-166286
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 GA75 see refer to the Upgrade Overview.
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 GA75 and Liferay Commerce 4.0 GA75 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, 10.6
PostgreSQL 12.x, 13.x, 14.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 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.
If you believe you have encountered a bug in the new release you can report your issue by following the bug reporting instructions.
Support is provided by our awesome community. Please visit helping a developer page for more details on how you can receive support.
Fixes
List of known issues
