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

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 GA76:
docker run -it -p 8080:8080 liferay/portal:7.4.3.76-ga76
Bundles and other download options
If you are used to binary releases, you can find the Liferay Portal 7.4 GA76 and Liferay Commerce 4.0 GA76 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-ga76
When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.
Features
Objects
Use relevant user information on notification template settings
New terms related to the current user and entry creator were
added, in order to improve the user experience when creating
notification templates.
Added terms:
-
[%CURRENT_USER_ID%]
-
[%CURRENT_USER_FIRST_NAME%]
-
[%CURRENT_USER_LAST_NAME%]
-
[%CURRENT_USER_EMAIL_ADDRESS%]
-
[%OBJECT_AUTHOR_ID%]
-
[%OBJECT_AUTHOR_FIRST_NAME%]
-
[%OBJECT_AUTHOR_LAST_NAME%]
-
[%OBJECT_AUTHOR_EMAIL_ADDRESS%]
https://issues.liferay.com/browse/LPS-171625
Enable configuration to define a field as unique data only
This feature allows the user to require that a field's values be
unique. When this is done, the system will not let two records have
the same value for that field.
https://issues.liferay.com/browse/LPS-135398
Experience Management
New date-time field available in Web Content Structures
Now users can create richer web content with the new
date-time field available in Web Content Structures. To
make it add more value, we also enabled the possibility to map
this new field to the editable of type date-time from any
fragment, allowing users to customize the date & time
values in content pages.




https://issues.liferay.com/browse/LPS-182417
New column on Content Dashboard (Review Date)
In order to improve the information we display at the Content
Dashboard, we’ve add a new column with the Review Date value. With
this new column, users have an easy way to view all contents where the
review is needed. In addition, we’ve developed a new Filter to give
the capability to show only the contents to be reviewed.
FILTER BY REVIEW DATE
-
All
-
To be reviewed
https://issues.liferay.com/browse/LPS-182032
Separate permissions of download and view documents in DAM
Users can be to set different permissions for download and for
view documents.
https://issues.liferay.com/browse/LPS-142644
Application Security
You are able to include users' first name in the notification templates as an Instance Administrator
The instance administrator can create the email templates
including the first name.
https://issues.liferay.com/browse/LPS-176074
Workspace
As a client extension developer, I would like to use a task to swap between live development mode and production mode
We’ve added support for creating custom client extension development
profiles in the same project.
For example, when the
user creates a file called client-extension.dev.yaml
, a
new task will be available to the user called deployDev.
https://issues.liferay.com/browse/LPS-180905
As a workspace developer, I would like to exclude modules from the workspace build
In order to allow developers to exclude directories from the
build, we’ve added a new property.
liferay.workspace.dir.excludes.globs=
https://issues.liferay.com/browse/LPS-173583
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 GA76 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 GA76 and Liferay Commerce 4.0 GA76 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 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.