Search Results

This article documents a known issue for users on Apache Tomcat 6.0.44, 7.0.69 or newer (including Tomcat 8) after Apache has issued a bug fix on those versions. When layout.parallel.render.enable=truehas been set, users might see the following errors in the console logs on Liferay...

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. The article addresses known errors that are thrown when updating the Notifications Portlet when using an Oracle...

This article is regarding a performance issue that may surface when executing an LDAP import using the UserGroup method for a large amount of users. Specifically, the issue is that the import process could take longer than expected. The cause of this issue is that the SQL query ("SELECT...

This article documents a known issue in the export process if any asset has a forbidden character in the name. These characters are usually reserved for HTML and XML and thus should not be used. In the case of exporting a page template as a .LAR, there is a console error and the export...

Liferay will support our API and resolve any issues and answer any questions having to do with the API itself or any other part of Liferay's software. Issues and questions regarding custom development may be handled by our Global Services team or by the developer of those customizations....

When strip.css.sass.enabled is set to true in the portal-ext.properties, a MalformedURLException will be thrown: ERROR [http-bio-8080-exec-1][VirtualHostFilter:323] java.net.MalformedURLException: Path null does not start with a "/" character java.net.MalformedURLException: Path null...

Between fix packs "portal-96" and "portal-109", there is a known issue with license handling. When the maximum connection limit is reached, the license page is displayed and the license itself is marked as invalid (see the picture below). You do not have the option to reset the...

When using patching-tool version 20 and below, corruptions of portal files can occur if a patch is installed when the portal is not completely shutdown, or if it is still running. Because of this, it is important to always shut down the portal completely prior to installing a patch....

Importing Large LAR files (100MB+) may fail in Liferay Portal. Below are some version-specific recommendations: For versions before DXP 7.1 Increase the size of the following property: com.liferay.portal.upload.UploadServletRequestImpl.max.size=104857600 Note: The default property within...

This article outlines known issues that exist in the Audience Targeting EE plugin for Liferay 6.2 and includes links to their respective tickets for more up-to-date progress on the particular issues. Resolution Please note that the following issues are related to the setup and usage of...

The fix on LPS-55208 modifies LDAPUserExporterImpl (PortalLDAPExporterImpl in Portal 6.2 EE) in a way that the user is only exported to LDAP when the user's modifiedDate field changed. When you change the password for a user only, then the call stack is a bit different and the user...

This article outlines a specific known issue that exists within Liferay Portal 6.2 EE SP9 and provides a link to follow its resolution. At the time of release, there is one notable known issue with Liferay Portal 6.2 EE SP9. In this version of Liferay, the thumbnail images of folders may...

This article documents a known issue in LPE-15180 where users are able to access web content functions without proper permissions. This vulnerability was fixed by the Portal-143-6210 Fix Pack. However, this fix was limited to only newly created web content. Resolution To patch this issue...

Liferay Support does not recommend or endorse specific third-party products over others. Liferay is not responsible for any instructions herein or referenced regarding these products. Any implementation of these principles is the responsibility of the subscriber. This article documents a...

This article documents a reported status code of 304 when using Apache 2 and Tomcat 7.0.42 connected via mod_proxy_ajp. In addition, the article provides a solution to fix the bug. Resolution The status code 304 is caused by a bug in Tomcat 7.0.42 and can be fixed with Tomcat 7.0.43 or...

This article addresses a known issue with Liferay Portal 6.2 EE. The issue is that web content displayed in the Asset Publisher portlet is not being updated after editing. As a reference, please see LPS-42282. Resolution As a workaround, add the following line to your environment's...

This article describes the issue with setting dl.file.extensions portal property preventing all Documents and Media file uploads, including using the multiple filder uploader. Steps to Reproduce Add the following to your portal-ext.properties found in the Liferay Home directory:...

If you try to deploy a portlet or theme or any .war file on a standalone JBoss 5.1, it will fail and try to create the directory in [Jboss_home]\jboss-5.1.0.GA\standalone\deployments Resolution The issue is that deployments are not put in the correct folder. Add the property...

This article describes known issues that have been encountered when publishing large files using Remote Staging. Resolution Affected Products Liferay Portal 6.2 EE SP5-SP10 Known Issue: Invalid checksum for LAR file error When the Staging server transfers the LAR file in smaller chunks...

After installation of a new hotfix, the dockbar fails to display and an error message can be found in the logs: ERROR [http-bio-8080-exec-1][LiferayMethodExceptionEventHandler:34]com.liferay.portal.kernel.portlet.PortletContainerException:...