Closed luyingwei80 closed 4 months ago
It should be slightly different from the situation described in the eighth item, but the displayed situation is indeed consistent with the one described in the eighth item, because I did not add any custom information to the database, only used the most primitive database. I tried searching in Simplified Chinese and couldn't get any feedback on anything I searched for, but searching for English names did show it. Does this mean that currently, the search function only supports English?
Updating the issue just now, I found that even searching in English can only search for very broad names, such as Glyph, which will display a portion. However, if I enter the full name of an item, such as Glyph of Mangle, it still cannot find results.
it should work generally.
can you check your DB if the _loc4 (thats zhCN) columns have data? (or _loc0 if you are searching in english)
Sorry, due to my limited understanding of database applications, sometimes the questions I ask may seem very childish and superficial to you. Please forgive me. Also, my English is poor, and many of them are translated through Google. If there are any words that do not convey meaning, please forgive me.
Are you referring to "* _loc4" as being viewed directly in a table in the database? Can you tell which table it is located in?
After reading your screenshot, I also tried searching with "贫瘠之地" and I am glad that it can indeed display the same search results as your screenshot.
But I also found another problem. If I search for "灵风", the system will still prompt that there are no search results, but when I search for "灵风头巾", I can still find it. It seems that wildcard search is not supported.
oh no D:
The problem is, that the seach ignores words with fewer than 3 letters. Which makes sense as you don't want to search for gibberish inputs or concatenations that are very common.
except
this doesn't work for languages where one "letter" is a word in itself.
should be fixed in 2c451b8deb28b5ee2b166ee1c0e2e9d9c87c855c
Your update is too fast^_^, I will go and update it. Also, after updating the code, is it still possible to use the "PHP aowow -- setup" command? I feel that the entire process takes quite a long time, and it seems that the system has been completely re executed.
use php aowow --update
when it's purely code changes like in this case, it's not required.
Just now during the installation process, there was a prompt:
16: 08:16 [WARN] GlobalStrings.lua not found for selected locale enus
[c] Continue any way? [r] Etry? [a] Bort?:
Although the installation process can continue, I'm not sure if there will be any other impact, or is it just a case on my end? Just for your reference.
Thank you very much. The issue with this search has been resolved^_^
GlobalStrings.lua contains the aliasses for emotes. As you don't use the enUS locale it should be irrelevant for you.
I found a problem, which should be my case here, where no matter what content I enter in the search box, it shows no search results. I don't know where the problem may be.