UPDATE: I made a mistake and hadn't set the matchContains option to true (which was the backend method we used). This ment that when I continued to add more characters it only kept the terms that started with the input query (using the cache - i.e. no new ajax request was made). However, as I had set the cacheLength to 1 I believe it shouldn't have used the cache at all but maybe it always caches the current result...
On 9 Juli, 14:33, cl2csand <mikael.san...@gmail.com> wrote: > When I use theautocompleteplugin with cacheLength set to 1 it still > seems to caches som queries. Although I have only seen the problem > with queries containing the characters (swedish) å, ä or ö. > > Maybe the problem lies there. To solve this I have to call the > flushCache function first in the formatTerm function which seems a bit > unnecessary. > > Eg: > > If I start to write "fö" it makes an ajax request and return say 25 > rows. If I then continue and write an "r" I only get a list of 3 terms > although about 10 items (of the first 25) contains "för". This time no > ajax request was made which makes me believe that it is a problem with > the caching. > > If I call flushCache in formatItem it always makes a new ajax request > with each modification of the search term and the correct results are > displayed.
