Info: Performing the steps described in this article requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.
The following sections provide solutions to common problems when working with Solr.
Changing the port
Port xxxx is already used, how do I change the port?
Start Solr from the command line with a different port:
<solr_install_location>/bin/solr start -p <NEW_PORT>
No results returned
Issue #1
I fill in an ‘a’ in the search field in Studio, but I don’t get any results. I am sure though that I have content containing an ‘a’.
Analysis: The Solr installation contains a file name stopwords.txt. All words that are listed in that file are not indexed.
Solution: Make sure that the stopwords.txt file does not contain any phrases that should be excluded from the indexing process.
Issue #2
When searching on terms with accents, no results are returned.
Make sure that the URIEncoding=”UTF-8” setting is included in the <tomcat path>/conf/server.xml file.
Issue #3
Entering a search term shorter than 4 characters or longer than 15 characters, no result is returned.
In case of a long search term you can split the term in two separate terms, each shorter than 15 characters.
Another solution can be to change the configuration. For more information, see Configuring Solr to control the search results in Studio Server.
Objects not indexed
Issue: The Health Check page shows OK but objects are not indexed.
Analysis: The Solr plug-in is probably not installed or enabled.
Solution: Verify the Studio Server Plug-ins page.
Comments
0 comments