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 GA31:
docker run -it -p 8080:8080 liferay/portal:126.96.36.199-ga31
For more information on using the official Liferay docker image
see the liferay/portal repo on
If you are used to binary releases, you can find the Liferay
Portal 7.4 GA31 and Liferay Commerce 4.0 GA31 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-ga31
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 Shipment Items and
can be modified from the Shipment Items Admin page. https://issues.liferay.com/browse/COMMERCE-8676
External Reference Code has now been added to Shipments and can
be modified from the Shipment Admin page. https://issues.liferay.com/browse/COMMERCE-8376
Is possible now to allow users to add categories and tags to an
object's entries. To have access to this feature, the user needs
to add the Categorization block, to the Layout.
In order to have a more scalable fragments baseline, we have
evolved how styles added to fragments in the Page Editor add added to
the page, moving them to specific CSS classes instead of adding them
inline. In addition to this, we have created a new data-lfr-styles
attribute, that allows fragment developers to decide which HTML
element inside a fragment will have the Page Editor styles
Finally, page creators can edit all the styles of a Fragment for
all viewports from the Page Editor, enabling a much easier way to
design mobile experiences. https://issues.liferay.com/browse/LPS-132571
With this new feature, we provide
clients with a way to restrict style customization capabilities for
specific roles, so that they can better control the level os styles
customization ensure consistent and homogeneous look & feel and
branding in an easier way.
Basic, limited and full styles
edition permissions for Content Pages edition are available now, as
well as a permission to provide access to the advanced options tab for
fragments edition in the Page Editor.
System admins can now choose to enable Publications during
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 GA31 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 GA31 and Liferay Commerce 4.0 GA31 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
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