Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Search Tuning modules must be deactivated when DXP 7.2 Service Pack 1 (SP1)/Fix Pack 2 (FP2) is configured with Solr 7

Written By

Tibor Lipusz

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

When DXP 7.2 is configured with Solr 7 and your patch level is Service Pack 1 (SP1) or Fix Pack 2 (FP2) or higher, if you navigate to the Search Tuning category on the Control Panel "Portlet is temporarily unavailable" error appears on page and errors are thrown in the console. This will be resolved under LPS-102609 and LPS-102611.

Resolution

Search Tuning features likes Synonyms and Result Rankings (available since SP1+/FP2+) are not supported on Solr. You must blacklist certain DXP modules that only work with Elasticsearch when DXP is configured to use Solr 7 as a search engine.

  1. Create a configuration file named com.liferay.portal.bundle.blacklist.internal.BundleBlacklistConfiguration.config
  2. Give it these contents: 
        blacklistBundleSymbolicNames=["com.liferay.portal.search.tuning.web.api","com.liferay.portal.search.tuning.web","com.liferay.portal.search.tuning.synonyms.web","com.liferay.portal.search.tuning.rankings.web"]
  3. Place the file in Liferay_Home/osgi/configs.

Related Articles

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?