Issues

Select view

Select search mode

 
50 of

JS and CSS resources are not being added to the <head>...</head> element for Liferay Content Pages

Fixed

Description

Problem Background:

This issue is caused by the failure of the Liferay Faces Bridge Ext module to detect the Portlet 3.0 HEADER_PHASE when a JSF portlet is deployed on a Liferay Content Page.

Steps to Reproduce:

  • Deploy the jsf-applicant-portlet demo to a Liferay DXP Content Page

  • Add the “jsf-applicant” to a Content Page

  • Reload the Content Page in the browser

Check Mark Expected Results:

  • The jsf.js resource appears as a child of the <head>...</head> element of the page. For example:

<head> <script type="text/javascript" src="http://localhost:8080/jsf-cp?p_p_id=1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn&amp;p_p_lifecycle=2&amp;p_p_state=normal&amp;p_p_mode=view&amp;p_p_cacheability=cacheLevelPage&amp;p_p_col_id=&amp;p_p_col_count=0&amp;_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_javax.faces.resource=jsf.js&amp;_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_ln=javax.faces" id="javax.faces:jsf.js" data-senna-track="temporary"> </script> </head>

Cross Mark Actual Results:

  • The jsf.js resource appears within the portlet <div id="..." class="liferay-faces-bridge-body">

Environment

None
Pinned fields
Click on the next to a field label to start pinning.

Assignee

Neil Griffin

Reporter

Priority

Created August 6, 2024 at 12:56 PM
Updated August 6, 2024 at 2:36 PM
Resolved August 6, 2024 at 1:01 PM

Activity

Show:
Neil Griffin
changed the StatusAugust 6, 2024 at 1:01 PM
Open
Closed
Neil Griffin
updated the ResolutionAugust 6, 2024 at 1:01 PM
None
Fixed
Neil Griffin
updated the DescriptionAugust 6, 2024 at 12:57 PM
h2. Problem Background: This issue is caused by the failure of the Liferay Faces Bridge Ext module to detect the Portlet 3.0 HEADER_PHASE when a JSF portlet is deployed on a Liferay Content Page. h2. Steps to Reproduce: * Deploy the jsf-applicant-portlet demo to a Liferay DXP Content Page * Add the “jsf-applicant” to a Content Page * Reload the Content Page in the browser (/) Expected Results: * The jsf.js resource appears as a child of the {{<head>...</head>}} element of the page. For example: {noformat}<head> <script type="text/javascript" src="http://localhost:8080/jsf-cp?p_p_id=1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn&amp;p_p_lifecycle=2&amp;p_p_state=normal&amp;p_p_mode=view&amp;p_p_cacheability=cacheLevelPage&amp;p_p_col_id=&amp;p_p_col_count=0&amp;_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_javax.faces.resource=jsf.js&amp;_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_ln=javax.faces" id="javax.faces:jsf.js" data-senna-track="temporary"> </script> </head>{noformat} (x) Actual Results: * The jsf.js resource appears within the portlet {{<div id="..." class="liferay-faces-bridge-body">}} *
h2. Problem Background: This issue is caused by the failure of the Liferay Faces Bridge Ext module to detect the Portlet 3.0 HEADER_PHASE when a JSF portlet is deployed on a Liferay Content Page. h2. Steps to Reproduce: * Deploy the jsf-applicant-portlet demo to a Liferay DXP Content Page * Add the “jsf-applicant” to a Content Page * Reload the Content Page in the browser (/) Expected Results: * The jsf.js resource appears as a child of the {{<head>...</head>}} element of the page. For example: {noformat}<head> <script type="text/javascript" src="http://localhost:8080/jsf-cp?p_p_id=1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn&amp;p_p_lifecycle=2&amp;p_p_state=normal&amp;p_p_mode=view&amp;p_p_cacheability=cacheLevelPage&amp;p_p_col_id=&amp;p_p_col_count=0&amp;_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_javax.faces.resource=jsf.js&amp;_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_ln=javax.faces" id="javax.faces:jsf.js" data-senna-track="temporary"> </script> </head>{noformat} (x) Actual Results: * The jsf.js resource appears within the portlet {{<div id="..." class="liferay-faces-bridge-body">}}
Neil Griffin
created the IssueAugust 6, 2024 at 12:56 PM

Flag notifications