Search Results

All Results 7011
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Unable to send message: Could not convert socket to TLS
legacy Troubleshooting
Issue In Fix Pack 92 we add the mail.session.mail.smtp.starttls.enable property to the portal.properties file to successfully configure the outlook mail server. After installing this Fix Pack or a higher one you...
Upgrade fails for bundle(s) due to "Table 'X' already exists" error
legacy Troubleshooting
Issue When running the DB Upgrade Tool, I'm seeing that my upgrade process fails due to an error that looks something like the following: Bundle X has invalid content in tables.sql:_create table X ... caused by ... Table...
LayoutFriendlyURLsException Thrown on Upgrade to 7.3
legacy Troubleshooting
Issue Upon upgrading to 7.3, a LayoutFriendlyURLsException was thrown on startup, even though no failures were present in the upgrade logs: WARN [Portal Dependency Manager Component...
Permissions with Web Content
legacy Troubleshooting
Issue Whenever the Guest and Site Member view permissions of the Web Content are removed, user is still able to see the web content added in the Web content Display Portlet. Environment Liferay DXP 7.0 Resolution This...
Using Virtual Instances on Liferay Cloud
legacy Troubleshooting
Issue Despite creating additional Virtual Instances for DXP and adding custom domain(s) to the webserver service, users are still redirected to the default Virtual Instance. Environment Liferay Cloud Resolution...
JavaScript Loader OSGI config settings don't appear to be applied following an upgrade to 7.2+
legacy How To
Issue When upgrading to DXP 7.3, we moved our previously modified OSGi .config files to the new bundle, but the settings from the JavaScript Loader .config file do not appear to be taking effect, as the default...
After upgrading to stack v4, the portal shows the message "This server has not been activated with Liferay Connected Services"
legacy Troubleshooting
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue After upgrading to stack v4, the portal shows the message...
Changes to Tomcat classloading order as of Tomcat 8+
legacy How To
Issue In Tomcat 7 and earlier versions, class loading for EXT JAR files were done in alphabetical order. However, with Tomcat 8 and later, class loading has been changed to be decided by the underlying file system....
Auto Upgrade in DXP 7.3 and Above
legacy How To
Issue Starting from Liferay 7.3, new upgrades for modules won't run automatically on startup by default. Resolution The following options are available to run the upgrades we may include in fix/service packs:...
How do I implement a JNDI database connection on Liferay PaaS
legacy How To
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue Portal Administrators may require a connection to the...
Unable to install .cfg file after updating or upgrading to DXP 7.3 Fix Pack 1
legacy Troubleshooting
Issue When placing a *.cfg file in the LIFERAY_HOME/osgi/configs folder an error is generated in the log: Unable to install .cfg file "{cfg-file-name}", please use .config file instead. Files with the *.cfg extension...
Local development Liferay bundle will stop working with IllegalStateException: Send redirect after commit
legacy Troubleshooting
Issue Portal developers running a local Liferay bundle with a developer Activation Key may suddenly be unable to use the server. The interface will redirect to /c/portal/license URL showing the License Server...
Delay when fetching data from headless-admin-user/v1.0/user-accounts for the first time after server restart
legacy How To
Issue When running a REST API call as below:...
Caching js_resolve_modules calls
legacy Troubleshooting
Issue The load time and the amount of data that is requested from the server by caching resolved_modules should be reduced. Environment Liferay 7.2 with DXP-8 Resolution A hotfix has been provided and below is the...
After upgrading a staged environment from 6.2 to DXP, the tag function does not work properly
legacy Troubleshooting
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...
Freemarker showing verbose exception
legacy Troubleshooting
Issue Freemarker is showing verbose exception on site, even though RETHROW is set. Environment Liferay DXP 7.2 Resolution The Journal Article error template can be configured with the following steps: Navigate to...
Is It Possible To Change Deployed War Location?
legacy How To
Issue The default location of the deployed war is ${liferay.home}/osgi/war folder. Is it possible to change the location?   Environment Liferay DXP 7.0+   Resolution You can use the following property to change the...
dl.file.rank.enabled property in Liferay
legacy
Issue Details on disabling the "dl.file.rank.enabled" property with the below queries. 1) The usage of this property? 2) What would be the impact on the system if disable it? 3) Will there be any impact on the...
Warnings get thrown while attempting to upgrade Lock_ table
legacy Troubleshooting
Issue Several warnings get thrown, while the migration tool is trying to upgrade Lock_ table. WARN [main][UpgradeProcess:446] Attempting to upgrade table Lock_ by recreating the table due to: You have an...
I Can Not Access Exploded War With DXP 7.0+
legacy
Issue With Liferay DXP, all the deployable wars move from {LIFERAY_HOME}/deploy into {LIFERAY_HOME}/osgi/war/ directory as a war file. But in Liferay 6.2 it used to be deployed as an exploded content into...