Search Results

Issue When upgrading from Liferay DXP 6.x to 7.4, the following Language localization issue has been observed: Languages / locales listed in the portal-ext.properties file are not available to be assigned for users Languages in "Available" column are shown as duplicates of "English (US)"...

Issue Import the object on the portal, the import was successful but after navigating to the 'Fragments and Widgets' option and searching for the imported object, it's now visible. Steps: Create a 'Demo' object with 2 text fields and publish it. Navigate to the 'Fragments and Widgets',...

Issue User wishes to know which MySQL version is supported in Liferay Cloud.   Environment Liferay Cloud Resolution Currently MySQL 5.7 is supported in Liferay Cloud. Additional Information MySQL  , content:...

Issue A custom Service Builder module functional in Liferay DXP 7.4 no longer works in a QR environment. Unsatisfied references appear when inspecting the custom Service Builder module. Environment Quarterly Releases: 2023.Q3, 2023.Q4, 2024.Q1 Resolution It is necessary to recompile the...

Issue Liferay's OpenID Connect implementation does not account for language variations for ui_locales. For example, Selecting English (United States) on Liferay sets ui_locales to en. Selecting Chinese (either Traditional or Simplified) sets ui_locales to zh. In this example, we would...

Issue When editing or creating a Language Key through Control Panel → Configuration → Language Override that includes umlauts, accents, or any other special characters, the value displays encoding errors and it is not stored correctly. For example, "Válido" could be saved as "Válido":...

Issue JavaScript added within the <@liferay_aui.script> taglib inside a web content template executes twice, leading to unintended behavior. For example: <@liferay_aui.script use="aui-base,aui-video"> console.log("Hello world!"); </@liferay_aui.script> The web content template is marked...

Issue 1. When the below content is pasted in the source of Web Content, then the onclick event gets removed from the source automatically. Below is the original content: <div class="Small-ButtonRSecond"><button class="Rbtn" onClick="">Read&nbsp;More<i class="bi...