Error when searching with Unicode string

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
6 years ago
I'm using Nop 4.0
Everything works fine but when I searched using unicode string it show error like this:

https://imgur.com/a/kut8T
please let me know what the problem is?
6 years ago
There's a known issue (changed in ASP.NET Core). We're currently looking into this

But I cannot reproduce your issue. It works fine on our demo site - http://demo.nopcommerce.com/search (at least with cyrillic chars)
6 years ago
Thanks Andrei.
Additional information: When I tried to install Nop using MSSQL Compact version it doesn't have this issue.

P/s: My test environment is "localhost" & "Azure app service with Azure SQL" (they're both have the issue).
6 years ago
I also see it works fine on the demo site.
Can I check if your demo site was upgraded from 3.9 or installed from a fresh 4.0 version ?
(I'm thinking if it's also related to DB as it doesn't have problem on SQL compact.)
6 years ago
Hello Andrei,

After tried many times here are some conclusions:
- Nop 3.9 - don't have "non-ANSII chars in URL issue"
- Fresh Nop 4.0 - have "non-ANSII chars in URL issue"
- Nop 4.0 upgraded from 3.9 - don't have issue with Search but still have issue when changing language with non-ANSII chars category/product name
- Nop 4.0 using Sql compact - don't have "non-ANSII chars in URL issue"

=> I think the issue was not from asp.net core but came from DB setting something like storedprocedures? Please check this with higher priority as it's going to be a serious problem.
6 years ago
sorry I was wrong. DB compact also have issue when changing language with unicode string.
So maybe it's not related to Db.
6 years ago
please remove this topic as it's from Nop-Template theme.
P/s: Sorry I'm newbie in Nopcommerce. When I installed a Nop package I didn't remove the plugin from their theme. I thought it will not affected to the website since the theme is not activated. Maybe they've used some code related to Route url (but it was still a problem in asp.net core)
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.