Search Results

All Results 7006
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Custom Themes are no longer shown as Site Templates in DXP 7.4
legacy
Issue In Liferay DXP 7.3, custom themes were seen under Site Templates Pop Up (Control Panel > Site > Choosing the template). However, in Liferay DXP 7.4, custom themes do not come under Site Templates, and...
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...
Builds fail due to org.jenkinsci.plugins.github_branch_source.ApiRateLimitChecker$RateLimitCheckerAdapter checkRateLimit
legacy Troubleshooting
Issue Jenkins is failing while creating the DXP cloud build and the following errors are observed: ERROR: org.jenkinsci.plugins.github_branch_source.ApiRateLimitChecker$RateLimitCheckerAdapter...
SSL errors when configuring a private repository in Liferay PaaS
legacy Troubleshooting
Issue You are using a private repository and while trying to configure it for the CI service you notice the webhook is not automatically created Also the following logs are shown in the INFRA environment Aug 13...
HTTP Strict-Transport-Security Header in Liferay
legacy
Issue Is HTTP Strict-Transport-Security Header enabled in Liferay? Environment Liferay DXP 7.4 Resolution Liferay enables HTTP security headers such as 'http.header.secure.x.content.type.options',...
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...
Workflow review has no edit option for Object entries
legacy Troubleshooting
Issue When reviewing an Object entry that was submitted to review, there’s no option to edit, whereas when doing the same for a Web Content article, there’s an option to edit it before approving the...
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...