Suppose I have a site that discusses deep, philosophical questions. I want to let users search for the meaning of life on the page meaning/life/search. Then, to generate revenue for my site, I add a matchmaking section. Users can search for the loves of their lives at love/life/search.

Since my users are impatient, I want to enable Fast Autocomplete (FAC) on both of these search pages. Each page has its own content types and search index.

Unless I am missing something, FAC allows me just one set of configurations, and it will be used on all search pages. (Yes, I can specify page-specific jQuery selectors for the search boxes, but the rest of the configuration is what bothers me.)

I am willing to do the work to enable search on multiple pages. (A client has requested this.) My question is, are you interested in adding this feature to the module?

This will require substantial changes to the public interface. For example, the backend-service classes, in their configurationForm() methods, return complete forms, including Submit buttons. If we want to configure multiple backends for different pages, all on the same config page, then that will have to change. The module will be responsible for the Submit button and pasting together the form fragments returned by configurationForm() implementations.

Similarly, the configurationFormSubmit() methods directly set the fac_* variables. If there are multiple backends in use, then the module will have to take care of saving the settings and passing them to the search() implementations.

Comments

benjifisher created an issue. See original summary.

benjifisher’s picture

I have created a sandbox project that implements the changes I suggested in the issue description. See the git log for detailed comments.

Marty2081’s picture

This feature is implemented in the 8.x-1.x version of the fac module.

Marty2081’s picture

Status: Active » Closed (won't fix)

I am not going to develop this feature request in the D7 version of the module.