This website uses cookies to ensure you get the best experience. Learn More.
Liferay Portal 7.4 GA37 and Liferay Commerce 4.0 GA37 Release
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 GA37:
docker run -it -p 8080:8080 liferay/portal:7.4.3.37-ga37
For more information on using the official Liferay docker image see the liferay/portal repo on Docker Hub.
If you are used to binary releases, you can find the Liferay Portal 7.4 GA37 and Liferay Commerce 4.0 GA37 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-ga37
When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.
Now users can easily customize the names of the fragments composing a page, by double-clicking on their names in the Page Editor’s browser. In this way, they will be able to understand better the components structure they have created.
https://issues.liferay.com/browse/LPS-147895
To help customers implement better experiences, we have added two features to fragments that make it easier to improve page load performance with the out-of-the-box components.
Lazy load configuration option for editables of type Image, including the out-of-the-box image fragment.
Option to set content-visibility to auto in Container fragment.
content-visibility
auto
https://issues.liferay.com/browse/LPS-147895
Modifications to pages within a publication will now render a preview of the page instead of just the data view. This will now allow you to quickly view a page from the application instead of navigating to the page. You can also view a side by side comparison between the current production page vs the new changes made in the publication.
https://issues.liferay.com/browse/LPS-158112
Previous to this update, users must be created under an account to belong to an account. This meant if the user was created for other means, they had to create a separate user to be assigned to an account. We felt this was unnecessary and removed this restriction.
https://issues.liferay.com/browse/LPS-149125
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 GA37 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 GA37 and Liferay Commerce 4.0 GA37 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 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