Search Results

All Results 6987
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Structure fields are not loading after upgrade from 7.2 to 7.4
Issue we have a problem with one of our journal structures after running the upgrade process from 7.2 fixpack-20 to 7.4u92. After the upgrade, the structure is empty when we try to edit in in Liferay (also when we try to...
Uploaded documents are available for all sites using different virtual hosts
Issue Create two sites Set a different virtual host for each site e.g. testsite.local, testsite2.local Upload a document into Documents and Media on your second site See that the uploaded file is available when...
How can I disable web content history?
Issue We would like to have only one version of our web contents so we want to to disable the web content history/versioning. Environment Liferay DXP 7.4 + Resolution Edit the Journal Article Maximum Version Count...
Font-weight is not being responsive on Heading Fragment
Issue Despite setting the font weight for the Heading Fragment, the fragment is unresponsive and doesn't respond to the applied setting.  Environment DXP 7.4 Resolution This is determined to be the intended behavior....
Enabling Special Characters for Screen Names and Passwords
Issue When trying to use special characters for setting screen names and passwords, not all special characters are accepted.  Environment DXP 7.0+ Resolution There is a simple workaround available to enable...
HTML Parsing errors when reindexing journal articles (jericho)
Issue In general, this error may occur after upgrading to Quarterly Releases. When reindexing or updating specific web contents, errors are displayed in logs similar to the following traces: ERROR...
Stack overflow and org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for servlet [Friendly URL Servlet - Public] threw exception
Issue There is a stack overflow error together with the error org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for servlet [Friendly URL Servlet - Public] threw exception Environment Liferay...
Screen name must not be duplicate but is already used by user SAML Error
Issue Some users can't log into Liferay via SAML when Liferay acts as Service Provider. There's an error in the logs about a duplicate screen name: 2023-11-30 18:04:53.521 ERROR...