Search Results

Issue When the web content size limit exceeds, there is no error displayed on the UI that the upload size is too large. Steps to reproduce: 1. Start Liferay DXP 7.4 U83. 2. Navigate to Control Panel > System Settings > Infrastructure > Upload Servelet Request. 3. Edit this to 104857...

Issue When performing an export operation, it takes too long. When it finishes, the resulting LAR size is much heavier than expected too. It applies to Staging as well. Environment Liferay DXP 7.3+ Resolution This may be caused because you AssetLink table is heavily populated. In 7.3,...

Issue The invalid extension document is uploaded with the valid extension name. Steps to reproduce: 1. Start Liferay DXP 7.4. 2. Navigate to Control Panel > System Settings > Documents and Media > Service. 3. Remove * from the 'File extension' and add .png, and .jpg in the file...

Issue In the earlier versions or updates of Liferay, the Control Panel Menu was hidden for specific users, and in order to achieve this, custom themes were being used. Hence a new feature is introduced directly in the UI wherein the control panel menu can be viewed by the users according...

Issue It's not possible to create a new pricing entry from the SKU side panel. There are no errors in the logs. Clicking on the plus button throws this error in the browser's console: Uncaught TypeError: A.LiferayItemSelectorDialog is not a constructor Environment Liferay DXP 7.4...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue Liferay service deployment fails when setting DXP 7.4 U98. In the Liferay service logs we can observe the following error: Caused by:...

Issue When the user tries to login, the email field is prepopulated with the company's domain name. This occurs when the login is unpopulated and user authentication is based on email addresses. Environment DXP 7.0, 7.1, 7.2, 7.3, 7.4 Resolution You may need to disable this feature by...

Issue We have some fragments similar to the one below <button> <span data-lfr-editable-id="text1" data-lfr-editable-type="rich-text"> ${languageUtil.get(locale,'exit')} </span> </button> We are trying to set the default translation dynamically with ${languageUtil.get(locale,'exit')} but...