Search Results

All Results 6987
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Updating React dependencies to later version
legacy
Issue As part of the security audit, the old version of the React might be vulnerable to attacks. Is there a way to hide the React version that Liferay displays? Environment Liferay DXP 7.3 Resolution At this...
tag is not working
legacy Troubleshooting
Issue Facing errors while using tag library <liferay-ui:input-editor> in JSP files. Environment Liferay DXP 7.4 Resolution The <liferay-ui:input-editor/> tag is deprecated as of Liferay DXP 7.1 in favor of...
Publishing Dynamic Data List linked page returns "No Access" error or returns to Staged environment
legacy Troubleshooting
Issue With local live staging, the linked page within the DDL returns to "Staged" page. With remote live staging, the linked page within the DDL returns a "No Access" error.  Reproduce Launch a Live and...
Reply button is not responsive when use Asset Publisher with Comments
legacy Troubleshooting
Issue When try to use a Asset Publisher using Rich Summary and Comments, the Reply button is not responsive Environment Liferay DXP 7.4 (equal to or above Update 88) Resolution Please request a Hotfix with...
When exporting a portlet, it takes much longer than expected
legacy Troubleshooting
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...
"Driver org.mariadb.jdbc.Driver claims to not accept jdbcUrl" error when trying to deploy 7.4 U98 + or 7.3 U34+
legacy Troubleshooting
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....
Remove prepopulated email domain from login portlet
legacy Troubleshooting
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....
How to create a default translation for editable fields in a fragment
legacy How To
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...