Search Results

All Results 7011
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Language Keys are processed as Literal Text in custom MVC Portlets
legacy Troubleshooting
Issue When creating a MVC Portlet that leverages language keys, language key output is presenting as the literal text, rather than the key value For example:  Language key in view.jsp: <b><liferay-ui:message...
ElasticsearchStatusException: Action/metadata line [1] contains an unknown parameter [_type]
legacy Troubleshooting
Issue When upgrading our Cloud Stack, we have found a problem with the Search Service. The following error is shown in the logs: Caused by: java.lang.RuntimeException: ElasticsearchStatusException[Elasticsearch...
No Documents are returned when using a Filter through Headless API
legacy Troubleshooting
Issue I am able to retrieve documents using the Headless API successfully if no Filters are specified. However, when using a Filter, no results are returned. This might happen when working with endpoints like...
Form View in Workflow
legacy
Issue When an admin receives the multi-step form created by Objects to review, the form data is visible on a single page instead of page by page. Steps to reproduce: 1. Create a multistep form with the help of...
Error trace related to Elasticsearch index_not_found_exception during the upgrade step KaleoDefinitionVersionUpgradeProcess#_upgradeKaleoDefinitionVersion
Troubleshooting
Issue We are upgrading from 7.0 to quarterly release 2023.Q4.8 During the upgrade step KaleoDefinitionVersionUpgradeProcess#_upgradeKaleoDefinitionVersion we are encountering an error trace related to Elasticsearch....
Blocked:origin errors are seen when deploying Spritemap CX
legacy
Issue Blocked:origin errors are seen in the browser console when deploying Spritemap CX. Theme SVG Spritemap is showing blocked:origin errors in a SaaS environment. Environment Liferay PaaS, SaaS Resolution Observing...
jUnit throws exception
legacy Troubleshooting
Issue We are encountering issues with jUnit and Liferay Spring MVC portlet. We have SubscriptionUtilTest class and when trying to run it by right click and run as "Junit" then throws error as...
Screen name should not be required when Autogenerate User Screen Names is enabled
legacy How To
Issue When enabling Autogenerate User Screen Names, the Object Action still mandates a Screen Name field, which is an inconsistency. The aforementioned behavior can be reproduced by doing the following...