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 GA66:

docker run -it -p 8080:8080 liferay/portal:7.4.3.66-ga66

Bundles and other download options

If you are used to binary releases, you can find the Liferay Portal 7.4 GA66 and Liferay Commerce 4.0 GA66 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-ga66

When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.

Features

Experience Building

Improved UX of Item Selector when several selection categories are loaded

Tab component is not scaling well when showing many types of elements inside item selector. Now, selecting items will be easier because the item selector will adapt from horizontal navigation tabs to vertical navigation menu, if more than 5 categories are present.

​​​​​​​Before (or less than 5 categories)

Now, if more than 5 categories

https://issues.liferay.com/browse/LPS-176216

Publications

You can preview fragment before publishing as a publication admin

Changing a fragment on a content page was not always obvious when previewing the whole page. We could surface these individual changes to a specific fragment more clearly if fragments can be previewed on its own.

Now as a publication admin you are able to preview fragment changes by itself.

https://issues.liferay.com/browse/LPS-176197

You are able to view the split desktop preview of a page as a publication user

There was a problem when previewing pages in a split view, the amount of space available causes the page to render in a mobile view.  This means you couldn’t do a side by side comparison of the desktop view.

Now as a publication user you can allow the user to view the entire desktop page even in split view.

https://issues.liferay.com/browse/LPS-175574

You are able to know log the conflicts that happens as a publication admin

Publications will prevent users from publishing data when it thinks there is risk of possible corruption. Many times though it is a false positive and the conflict is preventing something trivial.

While presenting the conflict to business users is usually unhelpful since the information can become overwhelming, we should have an option to log the information for support and developers.

Now publications admin can capture the data and present the information information so developers and support can provide more helpful direction for the end users.

https://issues.liferay.com/browse/LPS-175305

You are redirected to the current page when I create a new publication as a publication user

When you created a publication, you were almost always already on the page you wanted to change.  Redirecting somebody to the publication admin list was quite annoying as you needed to go back to the page you were already at.

Now as a publication user you can bring users back to the original page once the publication is created.

https://issues.liferay.com/browse/LPS-173412

Application Security

Motivation was to comply with the regulations governing cookies under the GDPR and the ePrivacy Directive sites must.

We implemented a new API to cover all of the required changes around cookies.

https://issues.liferay.com/browse/LPS-135623

SAML on site level configuration

With this new feature you can have your site with its own host to participate in the instance level SAML configuration driven SSO and SLO process as a site Administrator.
​​​​​​​
From now, once SAML is configured for the portal instance, SSO works identically to the instance’s default domain.
This new feature facilitates building solutions involving both SAML and sites with custom domains.

https://issues.liferay.com/browse/LPS-88244

You can use screenName as the external reference code to bind a user to a “oAuth2ApplicationHeadlessServer” client extension as a developer

The feature exists to enable a developer to make reference to a DXP user account in a reliable fashion.

Developers need this to configuring DXP via liferay-portal/OAuth2ProviderApplicationHeadlessServerConfiguration.java at master · liferay/liferay-portal

This feature Allows referring to a user account in a reliable fashion. screenName is more reliable than emailAddress because, during the bootstrapping of DXP virtual instances, it does not contain a variable part.

Developers can refer to a user account via screenName in (OSGi) configurations which can be reused across deployments.

https://issues.liferay.com/browse/LPS-173191

Search

Elasticsearch Sidecar Version Updated to 7.17.9

Liferay Portal 7.4 CE GA66+, Liferay DXP 7.4 Update 66+ bundled with the latest available version of Elasticsearch 7.x for Sidecar (7.17.9).

https://issues.liferay.com/browse/LPS-176650

Core Upgrades

The Verify Framework have been redesigning to make it more usable.

Verify processes can be added to modules. All module verifiers run when the module is upgraded. Two additional configuration options can be set for verify processes:

• InitialDeployment Verify Process: run the first time the module is installed.

• RunOnPortalUpgrade Verify Process: run anytime an upgrade in the Portal (Core) is executed.

To simplify verify process definition we have removed the OSGI property “verify.process.name” and now we use the bundleSymbolicName as reference for the Verify Process (modules can have more than one verify process)

In the Upgrade framework side, we have added an additional method to execute upgrade logic concurrently while having a batch to process the results. See this example of processConcurrently usage.

https://issues.liferay.com/browse/LPS-139576

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 GA66 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 GA66 and Liferay Commerce 4.0 GA66 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.

Fixes and Known Issues

• Fixes

• List of known issues​​​​​​​