12 April, 2020

Liferay 7.3

Lets have quick look how Liferay 7.3 looks. 

1) You would have docker ready image provided by liferay now

  docker run -it -p 8080:8080 liferay/portal:7.3.1-ga2

2) Dependency management improved
If some of you have used earlier version 7.0, 7.1 and 7.2 may aware that we had to add many compilation dependencies for liferay library it self which confusion got removed now and can be handle through single compile dependency which is really good.

compileOnly group: "com.liferay.portal", name: "release.portal.api", version: "7.3.1-ga2-3"

New Features

Liferay Portal CE 7.3 GA2 includes several new features mainly in Experience Management and some in Platform improvements.

Experience Management

We are continuing to empower designers and marketers to create user-friendly, beautiful and engaging experiences, without code freeing developers to focus on advanced interactive experiences through modern front-end tooling and APIs. Here are some of the new features you can find in this release.
Nesting layouts and more flexible layouts - The non technical users can now nest a layout into another one, and thus creating sophisticated page layouts using drag and drop. In GA1 the user could create horizontal layouts with multiple columns. But now it is possible to combine, split, nest, duplicate the layouts and thus unleashing the users’ creativity.
More info: LPS-102328

Workflows for Content Pages - Users can now define a workflow process for approval of creation and changes for content pages.  Just like for Web Content articles and other content types, administrators can specify a different workflow process at different levels: virtual instance level, site level and all the other entities (see workflow documentation). Once the workflow is enabled for the Content Pages, every new Content Page will go through the approval process before publication. Thus, the content reviewer can preview a page with pending status and approve, reject or request additional changes.
More info: LPS-103815
Support configuring permissions for Widgets in fragment-based pages - This feature allows users to configure permissions for widgets added to fragment-based pages (including: content pages, master pages, page templates and display pages). This will allow users to control which visitors can view the widget, so that some visitors may see it while for others it's fully hidden. It may also be used to configure other permissions such as allowing certain logged in visitors to configure the widget.
We’ve taken page templates and master pages into account as well. If you create a page based on a page template, all the widget permissions are copied to the page. The permissions in widgets from the master pages are set in the master page, so you cannot change them in the page itself.
More info: LPS-102583
One of our goals with the Rolling Releases is to respond faster to feedback so we want to mention some of the feature requested that we have implemented in this release.  Feature requests are new features our community members and customers would like to see added to our products, and also an opportunity to have your voice heard by using the voting system to support ideas that you would like to see implemented. The following feature requests were implemented in GA2:
Developers and Sysadmins
  • Allowing to enter longer values (255) for category names
  • Adding remote public Layout fetchLayout method
  • Ability to have autocomplete in the fragment editor for variables, taglibs and resources.
Page Designers / Administrators:
  • Visual identification of empty portlet-columns in Widget pages
  • More flexible configuration of the number of items display with RSS Publisher
  • Ability to hide/show portlet controls on the Widget pages
  • Ability to define navigation menus in Global to share them across all sites
  • Ability to store custom information relevant to my sites on the items of a navigation menu
Introducing Asset Libraries - with this new feature, it is possible to create dedicated libraries for content that make sense together and have better-isolated control on them. Asset libraries make it easier to reuse resources across different sites, connecting them only to the sites where you need to provide access.
Asset Libraries support the storage of documents and web content allowing a marketing team to organize collateral used in a campaign in an asset library and connecting it to the sites where the campaign will be run.  While creating a page, or writing a blog post, content authors can access the connected asset libraries and use images or content uploaded.

This feature is experimental, which means that before the launch of the Liferay DXP 7.3 GA1 some features may change, from the way to interact with the libraries, to the types of content that can be stored and reused. Additionally, you may find some differences in behavior that may affect existing applications. If you don’t want the new behavior, or are not interested in Asset Libraries, you can disable the feature in Control Panel -> Configuration -> System settings -> Asset Libraries.  More info on (LPS-102412, LPS-102471, LPS-102496)

(courtesy by https://liferay.dev/blogs/-/blogs/liferay-portal-7-3-ce-ga2-release )

Popular Posts

Featured Post

Liferay 7.3 compatibility matrix

Compatibility Matrix Liferay's general policy is to test Liferay Portal CE against newer major releases of operating systems, open s...