Skip to content

No search results when users display language set to Chinese (Taiwan) #4172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
71ian opened this issue Dec 23, 2024 · 2 comments
Closed

No search results when users display language set to Chinese (Taiwan) #4172

71ian opened this issue Dec 23, 2024 · 2 comments

Comments

@71ian
Copy link

71ian commented Dec 23, 2024

Version used
Ex: 4.4.1

Describe the bug
I have a search page setup using PnP Search Box, Search Results, Search Filters and Search verticals.
Users that have their display language set as English get search results as expected. Users with display language set to Chinese(Taiwan) receive no results: do not get a 'no results found message', simply there is nothing displayed at all except the search verticals web part.
If language set to English, searching using english or chinese characters is successful, with Taiwan language, neither English nor Chinese characters work.

To Reproduce
Detailed steps to reproduce the behavior:

  1. Set user display language to Chinese(Taiwan)
  2. Enter search term using either English or Chinese characters
  3. Result: Search results and search filters do not display

Expected behavior
Expect a successful search with results and available filters

Screenshots
Expected
image

Actual
image

Settings
image

Desktop (please complete the following information):

  • Browser: Chrome and Edge

Additional context
Add any other context about the problem here.

@kasperbolarsen
Copy link
Collaborator

can you try and have a look at the API calls , perhaps using this video as a guide if you are not familiar with the developer tool, https://www.youtube.com/watch?v=kPMSiRxK8H8

I am asking for the data that looks like this:
image

@71ian
Copy link
Author

71ian commented Jan 17, 2025

The issue is solved. This has been fixed in a newer version than what was installed.
thanks.

@wobba wobba closed this as completed Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants