Search Results

All Results 7011
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Commerce 2.1.x Breaking Changes
Commerce 2.1.3 & 2.2.0: When upgrading from 2.0.7, users must first upgrade to 2.1.0 and then to the latest version of Commerce. Commerce 2.1.2 COMMERCE-2309 & COMMERCE-4212: Discount Retrieval for Pricing Algorithm ...
Password Policies is inaccessible after upgrading from 6.2 to DXP 7.2
Issue After upgrading from 6.2 to 7.2, navigating to Control Panel > Users > Password Policies shows a UI error "Password Policies is temporarily unavailable", and an error is thrown in the logs: ERROR...
Commerce 2.1.0 Release Notes
New Features Improved Administration User Experience — Liferay Commerce 2.1 features an updated administration interface that makes the day-to-day work of managing a commerce site easy and efficient. Product,...
Full support for Unicode in a Liferay PaaS database
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue Emoji symbols can not be stored in database, for example as...
HTTP 400 response code shows sensitive data
Issue Sensitive system information may be seen in HTTP 400 - Bad Response status Environment DXP 7.0   DXP 7.1   DXP 7.2 Resolution The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code...
How to prevent content pages from scrolling unexpectedly when interacting with a portlet below the fold
Issue When interacting with a Liferay DXP portlet below the fold of a Content Page, the page unexpectedly scrolls to the top. The result of the interaction is properly displayed, but the user must scroll down to...
In Account Settings, Chrome autofills the "Job Title" field with the username
Issue When users update their password in the "Account Settings" section, Chrome will autofill the "Job Details" field: Environment Liferay DXP 7.0 Resolution Liferay is unable to reliably fix this issue as it...
Copy-pasting an image into a Web Content HTML field is stored as base64 characters
Issue When an image is copy-pasted into the Web Content editor, it is stored as a base64 collection of characters. What is the limit of this image? Are there any alternatives to this behavior? Environment DXP 7.0...