Search Results

All Results 7021
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Establish an external data source using JNDI
Issue Sometimes there is a requirement to use data sources other than Liferay DXPs. To do this, the data source can be configured via JNDI data source or JDBC properties. Any database other than Liferay DXP's...
Product status is not changing via headless APIs
Issue If the product is created via headless API with workflow-enabled. The status of the product is in a 'draft' state rather than a 'pending' state. Steps to reproduce: 1. Assign a default workflow to Commerce...
Subfolder webcontent is not fetched with headless API
Issue Step to Reproduce: 1. Create three basic web content. 2. Create a folder with two basic web content inside it. Now, total web content is 5 including. 3. Navigated to http://localhost:8080/o/api 4. Executed the...
"Unable to extend the HTTP session" WARN logs
Issue These warnings are frequently found in the logs:  Unable to extend the HTTP session. or Unable to extend the HTTP session. Review the portal property "session.timeout" if this warning is displayed...
INFO log traces with STARTED/ STOPPED information are not displayed when deploying a module if using WildFly/JBoss version 22.0.0 or higher
Issue When a module is started or stopped, there is usually a log trace of level INFO showing that information. However, when using the application server WidlFly/JBoss with version 22.0.0 or higher, these traces are...
Some pages do not display properly when HTTP Strict Transport Security (HSTS) is configured.
Please be aware that the page you are viewing has been machine translated from Japanese into English and may contain some translation errors. If you observe any issues with the translation, please contact us. Issue...
Intermittent performance issues caused by Journal Articles Display
Issue After installing dxp-16, intermittent performance issues are being seen Thread dumps taken during the performance issue show a number of threads with a similar format: at...
Starting nodes concurrently can lead to incorrect module upgrades
Issue Module functionality seems to fail after moving to a newer fixpack. After executing a system:check unsatisfied dependencies like the following appear: Component with ID 58 is unavailable due to missing...