Legacy Knowledge Base
Published Jun. 30, 2025

Fragments associated with Search Blueprints not appearing

Written By

Justin Mann

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Fragments and Web Content, primarily associated with Search Blueprints are not appearing or rendering on pages.
  • Potentially, this error may appear when starting up environment
FrameworkEvent ERROR 
com.liferay.portal.kernel.log.LogSanitizerException: org.osgi.framework.BundleException: Could not resolve module: com.liferay.portal.search.tuning.rankings.web [1032]_ Unresolved requirement: Import-Package: com.liferay.search.experiences.model; version="13.1.0"_ [Sanitized]

 

Environment

  • Liferay DXP 7.4
  • Quarterly Release 2023 Q4

 

Resolution

  • There is a bug in Quarterly Release 2023 Q4 that is causing Search Blueprint-related modules to not be deployed correctly.
  • As a result of these Search-related modules remaining undeployed, Liferay is unable to find any content to render in those fragments.
  • To resolve this issue:
    • set or request to have set, the following properties in the portal-ext.properties file
      • enterprise.product.enterprise.search.enabled=true
        feature.flag.LPS-129412=true
    • Perform a full reindex on the instance
Did this article resolve your issue ?

Legacy Knowledge Base