We are pleased to announce the release of Liferay Portal 7.4 GA34 and Liferay Commerce 4.0 GA34!
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 GA34:
docker run -it -p 8080:8080 liferay/portal:7.4.3.34-ga34
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 GA34 and Liferay Commerce 4.0 GA34 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-ga34
When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.
Features
Objects
Notification
Notification Queue allows users to verify the list of processed notifications. Will show messages already in the process of being sent (label Unsend), and messages that have already been sent (label Sent).
Furthermore, it is possible to resend a message already sent or require force action to send a message unsent using the kebab menu.
https://issues.liferay.com/browse/LPS-149051
Notification Attachments allow users to relate attachments from the same or other Objects to a Notification Template. Once related, when the actions are triggered, the notification will be sent with this archive.
https://issues.liferay.com/browse/LPS-155663
System Objects
Provide for customers a new System Object, Commerce Products, to integrate the Commerce environment. This new System Object contains the following fields: Name, Short Description, and External Reference Code.
https://issues.liferay.com/browse/LPS-151766
Provide for customers a new System Object, Commerce Product Group, to integrate the Commerce environment. This new System Object contains the following fields: Name, Description, and External Reference Code.
https://issues.liferay.com/browse/LPS-152408
Account Restriction |
Having the ownership defined by account means that only users with access to that account can access its data. This can happen via users that belong to those accounts or managers of the accounts through Liferay Organizations related to that specific account.
https://issues.liferay.com/browse/LPS-151877
Experience Building
Addition of CSS classes to fragments from the Page Editor
Now it’s possible to add new CSS classes to a Fragment, for faster and easier styling. These classes can be added to a given fragment instance, inside the Advanced tab of the Page Editor
Addition of custom CSS to fragments from the Page Editor
This can be done for each viewport, so that it is easier to quickly adapt pages to mobile layouts.
https://issues.liferay.com/browse/LPS-147511
|
Now users can define a friendlyURL to access a document, making it easier to identify. If not set by the user, the system will automatically fill it with the information from the document title.
Additionally, now documents embedded in other entities, such as pages, web content, etc, will use this friendlyURL to store the links. This friendlyURL share capabilities from other entities such as history of friendlyURLs so users that bookmarked the old url will be redirected to the new one. This also applies to your content, so now if you change the friendlyURL, title or filename of a document, the content that was referencing to this document will continue to display correctly the embedded assets.
https://issues.liferay.com/browse/LPS-113483
|
Now users can define a friendlyURL to access a document, making it easier to identify. If not set by the user, the system will automatically fill it with the information from the document title.
Additionally to adding friendlyURLs to documents, the display page template framework has been improved to take into account the history of friendlyURLs, so users accessing a display page for a document with an old friendlyURL will be redirected to the document with the latest friendlyURL
https://issues.liferay.com/browse/LPS-150453
|
When a column needs to be added, dropped or modified or a new table has to be created for an existing service builder module, this new API provides the tools to carry those operations out in the easiest way (without the need of executing buildUpgradeTable command anymore). BuildUpgradeTable is now intended to be used only for creating new tables.
Documentation
https://issues.liferay.com/browse/LPS-147861
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 GA34 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 GA34 and Liferay Commerce 4.0 GA34 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.


