Search Results

All Results 7006
Sort By
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Change of file names when documents are saved to data\document_library
Issue When saving files to the store, Documents and Media used to use the version label (e.g "1.0") as the file name (prior to Update 72). As of Update 72, file names look like this:...
Chances of vulnerabilities like SWEET32
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue How to fix the following vulnerability of the old cipher...
Sidecar Elasticsearch process is aborted
Issue Unable to restart the Liferay application server even after clearing temporary directories and 'An unexpected system error occurred' is showing on the UI. Following error appears in the log file:...
ConnectionPoolTimeoutException: Timeout waiting for connection from pool when full reindex
Issue As an Admin, users want to be able to decide if they want to cache extracted text when indexing so that if they are doing re-indexing they can disable this cache. In 7.4, there is an HTTP request call to S3...
Liferay 6.2 EE 173 and CVE-2024-25145
Issue We have found the following article CVE-2024-25145 Stored XSS with search results if highlighting is disabled, however it does not specify whether Liferay 6.2 EE 173 is affected or not. Environment Liferay 6.2 EE...
How to enable ModSecurity and Check if it's Working (Liferay PaaS)
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue How to enable ModSecurity in Liferay PaaS and test...
Avoiding 'q param' and caching of Favicon in the browser
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue Whenever users navigate to different pages, a new...
After upgrading, these ComboServlet errors are shown: 'Skip /o/js/resolved-module/... because its content type is not CSS or JavaScript'
Issue Errors like the following appear in the server's log file after an upgrade: ERROR [ComboServlet:389] Skip /o/js/resolved-module/frontend-js-tabs-support-web@2.0.12/TabsProvider.js because its content type is not...