Autosuggest not showing on search form

Presently it adds inline javascript to the page template in the $scripts output, so there is no additional JS file being added. You should be able to locate theData as a search query to make sure the javascript is in the page source.

It is likely that its not appearing or working because of the search block's [form] having a different CSS ID then the default AutoSuggest setting. Make sure that you specify the correct CSS ID for the search block [form] - you may need to use firebug or dig through the page source to determine this (ie: [form id="my-theme-search-block"] then in AutoSuggest settings make sure you specify it like #my-theme-search-block).

Basic install instructions have been added to the project page, but, there has already been a suggestion received on how to improve [eliminate] this requirement which should be implemented and released likely within the next couple days.

I'm not seeing JS either. And there's no "theData" in the page source. Anyway, the CSS ID is correct because I have my search form looking different now with this cool looking glass.

Why not to use drupal_add_js() and add autosuggest script as a separate file? It's much easier to find then, as well as to debug.

hey graker, drupal_add_js() is being used and the reason why its not its own separate file is because presently the CSS ID calls (which are a variable ID) are embedded into the javascript. So, the reason why there is no actual separate JS file is because you cant really dynamically generate static JS files all that well, or rather its probably not a good idea.

It was definitely a temporary approach for something that is in desperate need of improvement. I do know what I need to do to improve it and I should be able to get it taken care of today or over the weekend. Another small fix that will be coming with this next version is nodes with more then one url alias will only show up once now.

hey graker, drupal_add_js() is being used and the reason why its not its own separate file is because presently the CSS ID calls (which are a variable ID) are embedded into the javascript. So, the reason why there is no actual separate JS file is because you cant really dynamically generate static JS files all that well, or rather its probably not a good idea.

Actually you don't really need to generate JS files dynamically, you can pass CSS ID to JS as a variable (see drupal_add_js, $type='setting') and read it from Drupal.settings.[...] at JS runtime.

Another small fix that will be coming with this next version is nodes with more then one url alias will only show up once now.

BTW, what do you think about including recent search phrases from 'admin/reports/search' into the query?

ah wasn't aware of that will indeed check it out. essentially i would like to expand the search capabilities and include taxonomies and other things but at that point an indexed cache table of potential autosuggests is likely a good idea to keep performance in mind and the query small, because the more complex the query gets the slower it gets essentially. which is also compounded by the amount of items to search through.

wanted to apologize for the silence and not releasing and update as soon as i had anticipated but i do have a nice revision baking that will include a fix to the javascript selector mess. also included will be a resolution to the click to search dealio, will likely try to make it an option but basically what i originally pictured was suggested results main area, when clicked, would fill in the search box and perform that search (with the icon presently visible as a link directly to that item). primarily because the project this is being developed for is better geared towards that. have also got a basis for up/down/enter functionality so you can search and then press down arrow to skip through the results, pressing enter to fire the configurable action (search or goto node).

more ideas in mind but one step at a time. update soon hopefully.