Issues
- JS and CSS resources are not being added to the <head>...</head> element for Liferay Content PagesFACES-3716Resolved issue: FACES-3716Neil Griffin
- Remove the mobile phone field from the jsf-registration-portlet due to UsersAdminUtil being removed in LPS-195671FACES-3715Neil Griffin
- Remove the jsf-login-portlet due to AuthenticatedSessionManagerUtil being removed in LPS-199165FACES-3714Neil Griffin
- Upgrade to Apache Pluto 3.1.2 (Tomcat 9.0.83)FACES-3713Neil Griffin
- Upgrade to liferay-ce-7.4.3.ga102 and liferay-dxp-7.4.13-2023q4FACES-3712Neil Griffin
- Upgrade to liferay-faces-bridge-ext-5.1.3FACES-3711Neil Griffin
- Upgrade to liferay-faces-bridge-ext-6.1.3FACES-3710Neil Griffin
- Upgrade to liferay-faces-bridge-ext-7.0.2FACES-3709Neil Griffin
- Upgrade to liferay-faces-bridge-ext-8.0.2FACES-3708Neil Griffin
- Upgrade to liferay-faces-alloy-3.1.2FACES-3707Neil Griffin
- Upgrade to liferay-faces-alloy-4.1.2FACES-3706Neil Griffin
- Upgrade to liferay-faces-showcase-3.1.2FACES-3705Neil Griffin
- Upgrade to liferay-faces-showcase-4.0.1FACES-3704Neil Griffin
- Upgrade to liferay-faces-util-3.4.2FACES-3703Neil Griffin
- Upgrade to liferay-faces-util-4.0.1FACES-3702Neil Griffin
- Build failure with the yuicompressor-maven-pluginFACES-3701Resolved issue: FACES-3701Neil Griffin
- Upgrade to commons-fileupload 1.5FACES-3700Neil Griffin
- Upgrade to SLF4J 1.7.26FACES-3699Neil Griffin
- Migrate to Log4J2 2.17.1FACES-3698Neil Griffin
- Upgrade to Mojarra 2.3.21FACES-3697Neil Griffin
- ScriptsEncoderLiferayImpl does not strip the start <script> and end </script> elements from Liferay's ScriptDataFACES-3695Resolved issue: FACES-3695Neil Griffin
- Cannot find 'Portal Showcase' portal on 7.0.xFACES-3694Neil Griffin
- This page cannot be displayed normally on 7.0.xFACES-3693Neil Griffin
- butterfaces-applicant portlet cannot be deployed on 7.0.xFACES-3692Neil Griffin
- Error through after deploying com.liferay.faces.demo.portal.showcase.portlet-4.0.0.war on 7.1.xFACES-3691Resolved issue: FACES-3691UI Faces
- The demo usage of local services usage can result in a NullPointerException if the service is stopped after the isEmpty checkFACES-3690Resolved issue: FACES-3690Neil Griffin
- theme included portlet ajax navigation css include problemFACES-3689Neil Griffin
- PrimeFaces issue portlet does not invoke the file upload listener for the advanced mode use-caseFACES-3686Resolved issue: FACES-3686Neil Griffin
- Friendly url and h:link from faces bridge not workFACES-3685SE Support
- Move bridge alternative producers to a separate moduleFACES-3684Neil Griffin
- ElementNotVisible Selenium test failure with BootsFaces on Pluto 3.x and Mojarra 2.3FACES-3683UI Faces
- Selenium test failure with ICEfaces ace:fileEntry with Mojarra 2.3FACES-3681UI Faces
- Selenium test failure with RichFaces rich:fileUpload with Mojarra 2.3FACES-3680UI Faces
- Upgrade to version 4.3.0 of the Liferay Faces Bridge Impl dependencyFACES-3679Resolved issue: FACES-3679Neil Griffin
- Upgrade to Liferay DXP 7.2.10.sp6FACES-3678Resolved issue: FACES-3678Neil Griffin
- PrimeFaces 11 p:fileUpload fails on Pluto 2.0.3 + Tomcat 7.0.42FACES-3677Resolved issue: FACES-3677Neil Griffin
- Greeting does not visibly display in the BootsFaces archetypeFACES-3676UI Faces
- Registration portlet is unable to create a new user with Liferay CE/DXP 7.4FACES-3675Resolved issue: FACES-3675Neil Griffin
- liferay-faces-bridge-impl demo built with thin,cdi profile fails to deployFACES-3674Resolved issue: FACES-3674Neil Griffin
- NoSuchMethodException thrown by PlainTextCharUtil.getHTMLPlainTextCharCount(String)FACES-3673Resolved issue: FACES-3673Neil Griffin
- Develop thick-cdi module in order to support "thick" CDI portlet WAR deployment of the FacesBridge TCK on Liferay CE/DXPFACES-3672Resolved issue: FACES-3672Neil Griffin
- Remove support for Glassfish, Jetty, Resin, and Weblogic server deploymentsFACES-3671Resolved issue: FACES-3671Neil Griffin
- Selenium test failure in FACES_3250PortletTester on PlutoFACES-3670UI Faces
- Selenium test failure in JSFSPEC_1433PortletTester when the test portlet is deployed as a "thin" WAR in Pluto 3.1.xFACES-3669Neil Griffin
- Downgrade to hibernate-validator-5.4.3.Final for Pluto 3.1.xFACES-3668Resolved issue: FACES-3668Neil Griffin
- Support file upload restrictionsFACES-3667Resolved issue: FACES-3667Neil Griffin
- Bridge IPCPhaseListener does not use the Portlet 3.0 MutablePortletParameters mechanism of setting public render parameter valuesFACES-3666Resolved issue: FACES-3666Neil Griffin
- The portal:runtime use-case of the Portal Showcase should show the "Recent Content" portlet instead of "Hello World"FACES-3665Resolved issue: FACES-3665Neil Griffin
- JSF/Alloy/Portal ShowcasePortlet class must @Override renderHeaders instead of doView for Portlet 3.0 compatibilityFACES-3664Resolved issue: FACES-3664Neil Griffin
- InputRichTextDefaultValueTester fails on Liferay CE/DXP 7.4 due to a missing newline in the expected value for the submitted inputFACES-3663Resolved issue: FACES-3663Neil Griffin
50 of
JS and CSS resources are not being added to the <head>...</head> element for Liferay Content Pages
Fixed
Description
Environment
None
Pinned fields
Click on the next to a field label to start pinning.
Assignee
Reporter
Neil Griffin
Neil GriffinComponents
Affects versions
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 PMOpen
Closed
Neil Griffin
updated the ResolutionAugust 6, 2024 at 1:01 PMNone
Fixed
Neil Griffin
updated the DescriptionAugust 6, 2024 at 12:57 PMh2. 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&p_p_lifecycle=2&p_p_state=normal&p_p_mode=view&p_p_cacheability=cacheLevelPage&p_p_col_id=&p_p_col_count=0&_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_javax.faces.resource=jsf.js&_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&p_p_lifecycle=2&p_p_state=normal&p_p_mode=view&p_p_cacheability=cacheLevelPage&p_p_col_id=&p_p_col_count=0&_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_javax.faces.resource=jsf.js&_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
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
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&p_p_lifecycle=2&p_p_state=normal&p_p_mode=view&p_p_cacheability=cacheLevelPage&p_p_col_id=&p_p_col_count=0&_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_javax.faces.resource=jsf.js&_1_WAR_comliferayfacesdemojsfapplicantportlet_INSTANCE_pgzn_ln=javax.faces" id="javax.faces:jsf.js" data-senna-track="temporary"> </script> </head>
The jsf.js resource appears within the portlet
<div id="..." class="liferay-faces-bridge-body">