Search Results

All Results 6967
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Password Policies is inaccessible after upgrading from 6.2 to DXP 7.2 - workaround without rolling back to 6.2
Issue After upgrading from 6.2 to 7.2, navigating to Control Panel > Users > Password Policies shows a UI error "Password Policies is temporarily unavailable", and an error is thrown in the logs: ERROR [https-jsse-nio-8441-exec-4][PortletRequestDispatcherImpl:304] Unable to dispatch...
Permissions with Web Content
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 happens because Web Content's permissions are always overridden by the...
Using Virtual Instances on Liferay Cloud
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 To use Virtual Instances with your custom domains, add the following...
LayoutFriendlyURLsException Thrown on Upgrade to 7.3
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 Executor--1][PortalInstanceLifecycleListenerManagerImpl:146] Unable to register portal instance...
After upgrading to stack v4, the portal shows the message "This server has not been activated with Liferay Connected Services"
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 "This server has not been activated with Liferay Connected Services" on the...
JavaScript Loader OSGI config settings don't appear to be applied following an upgrade to 7.2+
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 values look to be in use. Environment Pre-upgrade environment: DXP 7.0 or DXP...
Changes to Tomcat classloading order as of Tomcat 8+
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. Environment Liferay Portal 6.2 Tomcat 8+ Resolution If the order that EXT...
'Nested Applications temporarily unavailable' error
Issue After upgrading to DXP 7.2+, I see that some Nested Applications widgets are not displayed on my pages and instead show a Nested Applications temporarily unavailable error. Environment Upgrading from DXP 7.0 to DXP 7.2+ Resolution This error specifically occurs if the Nested...
Jackson libraries are missing in Liferay 7.2
Issue I would like to use the Jackson libraries with the RestTemplate in Liferay 7.2 to convert messages to and from JSON, but receiving errors upon trying to use the MappingJackson2HttpMessageConverter.  Environment DXP 7.2+ Resolution According to this article the...
Search Results Pagination uses IP Address instead of DNS Name when NGINX is configured
Issue NGINX load balancer is set up in my environment. All URLs in the portal redirect using friendly DNS name. This does not work for the Search Results widget. When navigating the Search Results widget, it uses the IP address and not the friendly DNS name. Environment Liferay DXP 7.0+...
Unable to install .cfg file after updating or upgrading to DXP 7.3 Fix Pack 1
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 placed in the LIFERAY_HOME/osgi/configs folder are not read....
How do I implement a JNDI database connection on 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 Portal Administrators may require a connection to the database through a Java Naming and Directory Interface (following: JNDI)...
Auto Upgrade in DXP 7.3 and Above
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: Recover the old behavior with the property upgrade.database.auto.run set to...
ClassCastException in Xerces with JBoss EAP 7.3 and IBMJava
Issue When Liferay 7.3 is deployed on JBoss EAP 7.3 using IBMJava, the following exception is thrown at startup and the server fails to start: ERROR [ServerService Thread Pool -- 80][ServletContextHelperFactoryImpl:93] bundle com.liferay.portal.osgi.web.servlet.context.helper.impl:3.0.8...
Groovy Script to truncate the data of UserTrackPath Table
Issue If you want to truncate the data from UserTrackPath Table Environment Liferay DXP 7.2 Resolution Below is the Groovy Script which might help to truncate the data from UserTrackPath table. import java.sql.Connection; import java.sql.SQLException; import java.sql.Statement; import...
Upgrade to DXP 7.3 fails due to error about an already existing column
Issue When running the DB Upgrade Tool, the upgrade fails due to an error regarding a duplicate or already existing defaultvirtualHost column. (See examples of the error below) Upgrading Oracle DB Caused by: com.liferay.portal.kernel.upgrade.UpgradeException: java.sql.SQLException:...
What Is The Property Layout.url?
Issue What is this property and how it is invoked by Liferay? layout.url=${liferay:mainPath}/portal/layout?p_l_id=${liferay:plid}&p_v_l_s_g_id=${liferay:pvlsgid} Environment Liferay DXP 7.2 Resolution layout.url defines the format of the actual URL of the page layout. When a user...
Intermittent LDAP login failures due to LDAP response read time out
Issue With large LDAP directories, user login can sometimes fail if the LDAP query takes longer than the configured read timeout (default value is 500ms)  WARN [http-bio-exec][LDAPAuth:176] Failed to bind to the LDAP server with ... javax.naming.NamingException: LDAP response read timed...
How to resolve an IllegalArgumentException when attempting to update a Destination Worker's Core Size and Maximum Size
Issue When attempting to update the Worker Core Size and Worker Maximum Size (for example, changing the liferay/background_task destination name to a core size of 5 and a max size of 10), though the update appears successful in the UI, the logs show a "CM Configuration Updater" error and...
Delay when fetching data from headless-admin-user/v1.0/user-accounts for the first time after server restart
Issue When running a REST API call as below:...

該当件数: 8,739 件中 2,121 - 2,140