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 GA44:
docker run -it -p 8080:8080 liferay/portal:220.127.116.11-ga44
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 GA44 and Liferay Commerce 4.0 GA44 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-ga44
When using an IDE such as Eclipse or IntelliJ all apis are
immediately available in autocomplete for immediate use.
Users can provide this Theme CSS Client Extension with
the CSS files generated by the Theme build (Clay CSS and Main
CSS), and this Client Extension will allow them to add these
style resources to any page, without the need to deploy or re-deploy
the Theme anymore.
The renewed Page Editor provides more space and clarity for page
building, and a better page preview experience.
Users with advanced permissions can decouple all the styles from
their corresponding tokens, so that they have more freedom in page
building. In addition to this, the style inputs usability has been
improved and now users can pick a among a units dropdown in length styles.
Now users can disable, edit and localize the message in the
Collection Display fragment when no items are retrieved, to provide
better information to end users.
You can now segment users based on their country. To do so,
create a segment using the new “IP Geocoder Country” attribute. See
article for more details.
subtype of document in the Content Dashboard has been improved to
provide more detailed information about the file type of the document.
At a glance, users can now see whether the Document is an Audio file,
Image, Video, Presentation, etc.
Additionally the Type of asset (Blog, Web
Content or Document) is now clearly displayed in the Info Panel.
Content Dashboard Info Panel
changes have been implemented to ensure the upgrades run on time
before the server can process requests and to do not execute
unnecessary upgrades on startup:
module lifecycle has been improved to register events in
the proper moment. When the
PORTAL_INITIALIZED event is triggered, Core upgrade
processes should have already run and the companies will have been
initialized. Module upgrades start running when
PORTAL_INITIALIZED is registered and they must be
finished when the PORTLETS_INITIALIZED event is
Load initial data the first time a module is
deployed. You can use the new method
registerInitialDeploymentUpgradeSteps with that
Method to Initialize the Release_ table to the latest
schema version for new non-service module
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 GA44 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 GA44 and Liferay Commerce 4.0 GA44 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