Search Results

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 attempting to update our Jenkins CI image to use a...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue Can not install a hotfix due to folder permission...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). This article has been replaced by Deploying Changes via the CLI Tool...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). This article has been replaced by Initial Setup Overview on...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). You are starting your 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 Is it possible to install a third-party Jenkins...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue When navigating through most pages in the Liferay Cloud...

Creating and Upvoting Feature Requests As an open-source company, Liferay has always valued community feedback and suggestions to help us continually improve our products. To request...

Issue When using a Liferay DXP instance deployed on a Jakarta-based image (e.g., Tomcat 10), the liferay-dxp-agent bundle may fail to start. The logs will show an org.osgi.framework.BundleException error related to an unresolved package import. A key part of the error message will look...

Issue Booting Liferay DXP 2025.Q1 we see in log file following error: May 22 11:37:49.551 build-3994 liferay[liferay-7c588c8bd4-mg686] [dxp] ERROR [main][StartupAction:68] Files...

Issue We are trying to restore a PRO environment backup into DEV environment. And we see in the log several errors related to Document Library when decompressing: May 05 16:13:15.812 build-3964...

Issue When I navigate to Site Administration > Redirection > 404 URLs, all URLs show 0 requests Environment DXP 7.3 Resolution For the 404 URLs Requests counter to track the number of views, View Count must be...

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 we deploy a build (even if the image versions are...

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...

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 a user left our company (who had previously created a...

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...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue Now that the Liferay DXP image for a Liferay PaaS environment...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue When attempting to build a Liferay PaaS service, our Jenkins...

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue Liferay PaaS backup service will throw: ERROR 1227...

Issue Since our Jenkins builds are using Gradle Daemons, we would like to increase the memory available to control how much memory Gradle uses, so that it is increased from this default: org.gradle.jvmargs=-Xmx512m...