Issue
- Even though the hotfix that was generated by including LPS-146763 is installed, the following errors appear.
ERROR [default task-83][BaseJSPSettingsConfigurationAction:83] Unable to include JSP /search/bar/configuration.jsporg.apache.jasper.JasperException: java.lang.IllegalArgumentException: The string this-site,this-site does not correspond to a valid search scope preference at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:440) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473) ...........
at com.bluedart.hooks.filter.CrossScriptingFilter.doFilter(CrossScriptingFilter.java:77) at com.liferay.bluedart.security.GlobalSecurityFilter.processFilter(GlobalSecurityFilter.java:89) at com.liferay.bluedart.security.GlobalSecurityFilter.doFilter(GlobalSecurityFilter.java:55)
Environment
- Liferay DXP 7.2 Fix Pack 17
Resolution
- Custom plugins are the cause of the errors shown here, as shown in the error traces below.
-
at com.bluedart.hooks.filter.CrossScriptingFilter.doFilter(CrossScriptingFilter.java:77)
at com.liferay.bluedart.security.GlobalSecurityFilter.processFilter(GlobalSecurityFilter.java:89)
at com.liferay.bluedart.security.GlobalSecurityFilter.doFilter(GlobalSecurityFilter.java:55)
-
-
Workaround : The following are some pointers that could be useful in this type of use cases.
The problematic data is stored in theportletPreferencestable, users use Liferay APIs to get all preferences forportletIdsthat matchcom_liferay_portal_search_web_search_bar_portlet_SearchBarPortlet, they should all have a uniqueinstanceIdon the end as well.
Once they have the proper portletPreference entries, users should look for a preference"search scope"and remove duplicate values.
Additional Information
- We have a channel called "Global Service Team" for further assistance with customization or development suggestions.
- If the destination page is empty, the search bar portlet is temporarily unavailable
-
Please note, the customer use case is highlighted in this article, nevertheless, logs and workarounds could be useful for another similar use case.