Search Results

Issue SVG images are not visible on the patch level (Fix Pack 20) and they used to be visible on the previous one (Fix Pack 11) Reproduction Steps Setup Liferay DXP 7.1 with Fix Pack 20 Create a Basic document Upload the file with SVG extension → Publish Click on the 3-dots...

Issue Exporting Document Library to a LAR file from Content & Data -> Documents and Media -> top-right three-dot menu -> Export / Import won't export file versions. Environment DXP 7.0 or higher Resolution This is a product limitation and LAR can't be used to import all versioning files...

Issue The requirement is to get a list of all the site's names, as well as their creation dates and members. If there is a shortcut from the Liferay control panel?  Environment Liferay DXP 7.0 Resolution There is currently no OOTB functionality to achieve this. However, below is the...

Issue The requirement of adding an Email field to a form which would allow users to enter an email address that would receive an email with the information they filled out in a form. Environment Liferay DXP 7.2 Resolution There is currently no OOTB functionality to send the data of the...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue Can not change the level of verbosity to use for the Liferay-Portal field in the HTTP header in Liferay PaaS, even after setting...

Issue Steps to reproduce: 1. Create a structure with two fields(text and boolean) and also create a template for it in a Global site. 2. Go to "Liferay DXP" site and create two new WebContents with previous structure and check the boolean for the first one and leave uncheck for the...

Issue After changing, the root context path to custom context the commerce components and system settings taking more time to load. Steps to reproduce: 1. Start Liferay with Commerce installed. 2. Change the ROOT folder name (under{LIFERAY_HOME}/tomcat-9.0.37/webapps/ROOT) to 'myportal'....

Issue When SAML module is configured and integrated with an Azure B2C and we need to map a parameter to a Liferay parameter, a problem might occur due to a whitespace: <saml:Attribute FriendlyName="Given Name" Name="Given Name"...