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 GA30:
docker run -it -p 8080:8080 liferay/portal:126.96.36.199-ga30
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 GA30 and Liferay Commerce 4.0 GA30 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:
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-ga30
When using an IDE such as Eclipse or IntelliJ all apis are
immediately available in autocomplete for immediate use.
External Reference Code has now been added to Shipments and can
be modified from the Shipments Admin page https://issues.liferay.com/browse/COMMERCE-8376
Through this functionality will be
possible for the users to relate system objects with custom objects
using a many-to-many relationship.
You can relate
multiple entities from the current Object to multiple entities in
another Object. When selected, a new database table is created for
both sides of the relationship.
Once conditions are enabled, just
the entries that match with the condition will start the action
execution. To create this condition will be possible to use
expressions and all fields from the object. The
conditions will be able to work for any entry, triggered by an add,
update or delete.
Now it is possible to choose which redirection type will Liferay
use to redirect users when accessing old friendlyURLs for pages or
display page templates.
When locale.prepend.friendly.url.style is set to 0 we were
using the 302 code for redirecting the users. Now it is possible to
configure it to 301, for example if your site has just content in the
default language. https://issues.liferay.com/browse/LPS-155163
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 GA30 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 GA30 and Liferay Commerce 4.0 GA30 were tested
extensively for use with the following Application/Database Servers:
MySQL 5.7, 8.0
PostgreSQL 12.x, 13.x
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.
List of known issues