I had a field in two different views on the same project that were using this to convert textfield to autocomplete. Worked on first install but by the next day after additional work, it stopped working. I tried everything I could, failed and I noticed the respective field had an autocomplete=OFF attribute in the HTML output.
The following discoveries made it work again:
1.) In each views I had one other taxonomy term set to autocomplete (rather than dropdown) along with an additional field set to dropdown mostly
2.) In addition I had the target exposed textfield set to autocomplete using the checkbox provided by VWF, I was indifferent to position (order) of the field among the other exposed filters.
Turned out that introducing the additional two bullets above prevented the VWF autocomplete from working, it just spins and returns "x returns no result. Try something else." even when I was very sure the search terms contain those letters/phrases or words.
I resolved this situation by setting bullet one above to just dropdown and then positioning bullet two in the middle or ensuring it is not the last exposed field. After saving the changes, I then returned the setting for bullet (1) to autocomplete. Everything works this way.
With just one exposed field it works fine. I think this is not a good dependency and should be looked into or at least have it stated in the Tips & Tricks section of the module page. I hope this helps someone to avoid days of wonder and surprise like I had to go through.
Regards,
Ojchris
Closed: outdated
1.2
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.
And thanks for participating and using the module.
p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.