No search result in WebEA when search term contains foreign characters

[miksko]

Hi,

We are experiencing a problem with the Search functionality in WebEA. We are using Swedish in the Sparx model, which means you sometimes search for elements containing national characters like å, ä and ö. As you notice it works fine to use those caracters in the forum. But when you use them in your search string in WebEA, the application returns an empty result.

Does anyone else experience the same problem with the German ü, the French á or the Spanish ñ? Have you been able to work out a solution in that case?

Mikael

[skiwi]

This could be opening a can of worms!
You need to check your unicode enablement across the entire stack - HTTP server, PHP, perhaps your database settings.
And EA may also have problems, it appears to have difficulty with certain types of data entry fields, keyboard settings, and code pages.
Good luck

[miksko]

Thanks for your reply Skiwi. Can of worms or not: A search function becomes a nuisance if it isn't working reliably, so we have to either solve it or block it.

[nilspc]

Hi,

Any progress on a solution for this?
Also in Sweden and we see the same problem, but what we also see is that the search works fine in Prolaborate running in IIS against the same PCS and repository so the problem appears to be caused by WebEA and not by configuration in IIS or SqlServer.

/Nils

[miksko]

Hi Nils,

We found some settings in the configuration file (for PHP) that could/should be altered. But altering them to their recommended values did not change anything. The PHP module we intended to affect this way was mbstring, which is used for multi-byte encoding of foreign characters, for example UTF-8.

We will escalate this problem to the support. I'll try to remember to post the result here, when we get it.

Mikael

[miksko]

Hi again Nils, and other ones who follow this thread.

We finally received the following reply from the Sparx support: "Unfortunately it's not currently possible. I will submit a feature request on your behalf so that this is considered for implementation in a future release."

"Feature request" is a common euphemism for things most users would consider a bug, but that is obviously the best we will get.

[Geert Bellekens]

Hi again Nils, and other ones who follow this thread.

We finally received the following reply from the Sparx support: "Unfortunately it's not currently possible. I will submit a feature request on your behalf so that this is considered for implementation in a future release."

"Feature request" is a common euphemism for things most users would consider a bug, but that is obviously the best we will get.

In 2023 I think we can expect applications be able to handle more than only the English character set.
Anything less I definitely consider a bug.

Geert

[nilspc]

Hi,

Thank you for the update 

/N

[miksko]

Hi,

Just want to close this topic by happily reporting that the bug has been solved in an update. The Search functionality now works happily with foreign characters (at least Latin-1).

Mikael