AjaxSearch 1.9.0 - Next features ?

Here are some suggestions. Some of them are already developed and will be part of the next release.
But I am interested to know which features interest you.

Don’t hesitate to add any suggestion.


==== Several AjaxSearch simultaneously on a page - Unique id for AjaxSearch instance

This will allow to have several search inputs on a same page.
For instance a site wide search on the upper left of your site and a specific search for some items on a dedicated page.


==== Define categories and display the results per category

&category [ tv_name | ’’]
Name of a TV. This tv define the tag which marks the category
Results will be displayed grouped by category or mixed.
Each group of results could be displayed with its own result template and its own pagination



==== Define sites and run several search with one search term

&sites : [comma separated list of sites] (optional)
sites allow to define sites where to do the search. By default MODx.
Could be used to merge results from customs databases/tables (e.g: wordpress) and MODx results


==== Custom output

&output [ 0 | 1 ]

0 - by default the results are listed below the input form
1 - custom layout:

To place the different AjaxSearch elements where you want, by using:

[+as.inputForm+] : the input form with the intro message
[+as.results+] : the search results


=== Allow $_GET requests for Google Analytics

Use $_GET or $_POST for a better Google Analytics integration


=== AjaxSearch 2.0 for Revolution

Do not add anything more , forget the version 1.9 and start the version 2.0 for Revolution.

Even if the version 1.9 has been entirely refactored for an easier migration to Revolution,
the model part (MVC pattern) should be refactored for xpdo and adapted to MODx Revolution.

I’d also like to be able to specify sections of the Site Tree to exclude from the searches, too.

thanks coroico!

...tried to tick off all of’em

I’d love to see a version of AjaxSearch for Revolution.

In any case, thanks a lot for your efforts!

Opensearch out-of-the-box, although this may currently be possible with out too much effort.

The votes are now closed ...

The AjaxSearch 1.9.0 beta is now available here See the ajaxSearch download menu option in the ajaxSearch area.

The new features implemented are:

==== Several AjaxSearch simultaneously on a page - Unique id for AjaxSearch instance

- non ajax demo - ajax demo -

This will allow to have several search inputs on a same page.
For instance a site wide search on the upper left of your site and a specific search for some items on a dedicated page.


==== Define categories and display the results per category - non ajax demo - ajax demo -

&category [ tv_name | ’’]
Name of a TV. This tv define the tag which marks the category
Results will be displayed grouped by category or mixed.
Each group of results could be displayed with its own result template and its own pagination


==== Custom output - non ajax demo -

&output [ 0 | 1 ]

0 - by default the results are listed below the input form
1 - custom layout:

To place the different AjaxSearch elements where you want, by using:

[+as.inputForm+] : the input form with the intro message
[+as.results+] : the search results

For the moment runs only for the non-ajax mode. It still remains some weirds issues with the ajax mode.


=== Allow $_GET requests for Google Analytics

Use $_GET or $_POST for a better Google Analytics integration


==== parents ( in / not in) (demo here)

&parents [ [ in | not in ] : comma separated list of Ids | ’’ ]

e.g:
&parents=`in:24,25` - do the search in the children documents of documents 24 and 25

&parents=`not in:24,10` - do the search in all documents except in the children documents of documents 24 and 10 documents

&parents=`24,25` means &parents=`in:24,25` (compatible with the 1.8.4 release)
&depth [ 0 < int ] Number of levels deep to retrieve documents



==== documents ( in / not in) (demo here)

&documents [ [ in | not in ] : comma separated list of Ids | ’’ ]

e.g:
&documents=`in:28,29,30,31` - do the search in the documents 28,29,30,31

&documents=`not in:28,29,30,31` - do the search in all documents except in documents 28,29,30,31

&documents=`28,29,30,31` means &documents=`in:28,29,30,31` (compatible with the 1.8.4 release)


==== filter (demo here)

filtering by tv name is now possible

e.g: &filter=`articleTags,volcano,7` display only documents related to volcanoes.
Documents are filtered by the TV ’articleTags’.


Any help to redo the input demos with IE, Safari and Chrome are welcome. Uses the ajax demos listed on the left menu. These tests are mandatory before to release the final 1.9.0 version.

Thanks for your feedbacks.

Gah, does that mean the subSearch function is out? I just got it working in 1.8.4 today, and found this thread when looking to see if I could somehow switch the radio buttons to checkboxes so that people can search more than one parent directory if they wish to.

Is there an alternative?