Posted by WorldFallz on May 22, 2008 at 5:57pm
Jump to:
| Project: | Node Quick Find |
| Version: | 6.x-1.2 |
| Component: | User interface |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (cannot reproduce) |
Issue Summary
I have a site with about 1500 nodes, but I'm only using about 4 content types with quick find (so the pool is less than tha), and there is a significant delay between the end of the circular animation and the presentation of the drop down box-- so much so my users think it's not working or the results are empty.
I'm using the "patch" from http://drupal.org/node/244242, I don't know if that has anything to do with it.
I took a look at the code, but i know nothing about the autocomplete js-- if you have any ideas what might be the problem, I would be grateful....
thanks.
Comments
#1
Number of nodes is irrelevant - the result set should always be 10. Title and Type have, I believe, indexes - so this shouldn't be a problem.
Do you have any problems with any other auto completes?
#2
No... I'm actually using the dynosearch module temporarily (I prefer the functionality of this module) and that autocomplete works perfectly.
I did a little more troubleshooting, and it seems if I remove the patch from http://drupal.org/node/244242 the problem goes away, but then it doesn't return any results if i have more than one content type selected. Since I have to be able to specify multiple content types that's not a viable solution.
I tried playing around with the code in the patch, but nothing seems to work except reverting back to the original module (which doesn't work with multiple content types).
#3
I'll have a play with the module under dev - will try out the devel module to generate several thousand nodes...
Cheers,
Nick
#4
I cannot reproduce this.
#5
same thing here, I think it's something to do with the Drupal core autocomplete js, nothing to do with this module.