Search Results

All Results 6974
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
In DXP, it is not possible to differentiate configuration per site on embedded portlets
Issue In DXP, a portlet could be embedded like below: <#assign preferencesMap = {"portletSetupPortletDecoratorId" : "barebone"} /> <@liferay_portlet["runtime"] instanceId="1234"...
Guests can no longer see web content articles
Issue After updating a Liferay DXP 7.2 server to dxp-5+ and publishing content Guests no longer see web content articles. A fix, LPS-106146, was introduced in dxp-5 that addressed a permissions error when...
Why p_p_auth token is exposed in the URL? Could it be a security risk?
Issue On Liferay Portal 6.2, p_p_auth token is exposed in the URL. It might be considered as a security risk. Environment Liferay Portal 6.2 Resolution No attacker or other user can use p_p_auth token, only a...
Getting the themeDisplay object in DXP themes and layout templates
Issue In Liferay Portal 6.2, the themeDisplay object was inherited in themes and layout templates. How is it possible to get the same object in DXP? Environment Liferay DXP 7.0 Liferay...
Cannot Request Users With long userid After Patching to DE-93
Issue We use this code to secure our API calls in our customization: (request variable is an HttpServletRequest object from @Context annotation) long userId = GetterUtil.getLong(request.getRemoteUser());  user =...
Changing layout's type removes portlet preferences
Issue Changing our page's type from "Layout" to "Link to URL" then back to "Layout", the page won't retain its portlets configuration Environment Liferay DXP 7.0 with Fix Pack 93 or below Resolution The...
Checking the different fixes between two hotfixes
Issue We have two hotfixes and we would like to know the difference between them How can we check the common and different fixes within those hotfixes? Environment Liferay Portal 6.2 Liferay DXP 7.0+...
Contributed Fragment Collection's content is not correct after deployment
Issue We have created a Contributed Fragment Collection, carefully following the documentation The collection contains two fragments After successful deployment, we see only one fragment is present twice...