When entering place names for example birth or death, I normally start typing and a dropdown appears with options containing the typed string.
That is OK.
Apparently there is a limit of 10 found places in the dropdown.
Now I have an issue with some short placenames (in the Netherlands) like Uden or Loo.
These are names that produce a long dropdown list, because there are a lot of placenames in the database containing these strings.
For example the name Uden produces in my case:
Crudenburg, Nordrhein-Westfalen, Duitsland
Freudenstadt, Baden-Württemberg, Duitsland
Gudensberg, Hessen, Duitsland
Judenburg, Steiermark, Oostenrijk
Lüdenhausen, Nordrhein-Westfalen, Duitsland
Lüdenscheid, Nordrhein-Westfalen, Duitsland
Oudenaarde, Oost-Vlaanderen, België
Oudenbosch, Noord-Brabant, Nederland
Oudenrijn, Utrecht, Nederland
Rauden, Sachsen, Duitsland
... but NOT the place I am looking for: Uden, Noord-Brabant, Nederland
In webtrees 1.7 I was able to type on more characters like Uden, N and then the right place eventually appears in the dropdown list.
But in Webtrees 2 it does not.
It looks like if the search is done only on the first part of the placename.
The problem now is that my editors do not find the correct placename and think it does not exist yet.
Then they are entering the name as a new one and sometimes make typos, so duplicates arise.