Search Results

This article outlines a practical suggestion for avoiding issues when using multiple languages in a site along with the Liferay platform’s staging feature. Following this suggestion will help prevent future staging publication failures.  Resolution When utilizing multiple languages...

By default, Liferay encrypts the passwords that go into the database. The default algorithm is SHA-1 in 6.0 and 6.1 versions, which changed to PBKDF2WithHmacSHA1/160/128000 in version 6.2. The encryption algorithm can be changed and even turned off via the portal-ext.properties. Because...

This article outlines a practical suggestion for keeping data in sync between the staging and live site for portlets that allow changes in both places. Following the workaround will help prevent staging publication errors and failure. Resolution Generally, if staging is enabled for a...

This article describes how numeric screennames can be used in Liferay Portal. Resolution Set the following property to true in the portal-ext.properties file that will override the default functionality of being unable to create numeric screennames. # Set this to true when you want the...

The principles below are adopted from general industry standard patch management best practices. Following these will help mitigate the risk of change on production servers. Awareness Liferay communicates the availability of maintenance updates for Liferay products through Announcements....

In Liferay Portal, after completing a large LDAP import, performance may suffer because Lucene is set to re-index after every change. For example, if there are 15,000 users, Lucene will perform an index after each user is added, which will result in 15,000 index commits. This slows down...

This article describes a fundamental product limitation when pjax is used to render programmatically nested content in Liferay platforms. (Pjax is a jQuery plugin, a standalone JavaScript module that uses AJAX (XmlHttpRequest) and pushState() to deliver a fast browsing experience.) This...

When installing Liferay Digital Experience Platform (DXP) 7.0 or any Liferay Portal version, portal administrators have the option to leverage any of the translations that come with the default installation. This article outlines the best way/s to correct these translations. Resolution...

This article describes how specific LDAP attributes can be ignored during LDAP user import. Sometimes, users may change some information on the Liferay Portal. When the next scheduled LDAP import is executed, it will overwrite the user-made change. To ensure the change is not...

The title of a portlet is determined by the language properties files and may be changed system-wide by using a language ext properties file similar to portal-ext.properties. Resolution To demonstrate how to change the portlet titles, this article we will seek to change the title of...

Through the Blog Portlet, there is a unique functionality where Blog information can be split into different pages. Resolution To achieve this functionality, start by going to the wrench in the portlet and scoping the portlet to the specific page. This would make the scoped portlet...

In most cases, optimizing Lucene is helpful; in larger deployments it is a necessity. This article aims to explain the relevant settings for optimizing Lucene and provide links to further information. It must be mentioned, though, that this service is not supported by Liferay...

When an email notification is sent out, the template for the message may not be referencing the correct port within the URL. For example, the email may show the URL as "http://www.liferay.com:8080" instead of port 80. Resolution To resolve this issue, add the following properties to the...

When using the AIX operating system with Liferay Portal 6.1, a license may fail to deploy, giving the output: License is in use by another instance. Resolution This license issue is due to a known issue with AIX, in which neither ipconfig nor ifconfig will return the mac address for the...

This article documents a known behavior where Message Boards' CKEditor—when configured to HTML—will have text stripped from hyperlinks after a post. This is usually observed after setting the protocol to Other. Resolution This behavior is expected under Liferay DXP's Antisamy...

When searching, guest users are able to see highlighted folders, categories, and threads when they have no permission to view them. Resolution During search, Liferay runs a permission check on each of the results to see if the user that is searching has rights to view the result in...

Activation Key deployment for Liferay Portal versions 5.2.9 (Service Pack 5) to 6.0.x is different from key deployment for Liferay versions 5.2 SP4 and earlier. Activation keys are no longer generated based off the Server ID. Instead, you'll need an .xml key file. This file will be...

CVE-2018-3831 reports that, "Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue when secrets are configured via the API. The Elasticsearch _cluster/settings API, when queried, could leak sensitive configuration information such...

This article is a legacy article. It applies to previous versions of the Liferay product. While the article is no longer maintained, the information may still be applicable. In older versions of Liferay Portal (e.g. 5.1.x, 5.2 EE SP3), by default, Liferay will import all user groups a...

The following Common Vulnerabilities and Exposures (CVE) have been reported for Apache Struts 2: CVE-2017-9805 CVE-2017-12611 CVE-2018-1327 - REST XStream FreeMarker CVE-2018-11776 How are Liferay DXP (both 7.0 and 7.1) and Liferay Portal affected by the Apache Struts 2 Vulnerability?...