AjaxSearch 1.9.0 beta and a new demo site ...

AjaxSearch 1.9.0 is coming soon ... and a new demo site too.

Find the first demos of the beta release of AjaxSearch 1.9.0 on this new site

For the new features go to the ajax mode and non-ajax mode sub menu. I have also written 3 posts in the internet cafe section about the 1.9.0

I have rewritten the Js scripts (mootools 1.11, mootools 1.2, jquery 1.3.2). And all the input form tests (15 demos) have been passed with firefox. Any help to pass these input form demos with others browsers (IE, Safari, Chrome) is welcome. Thanks to leave your tests results as a post.

The site is under construction, so some contents are still missing and some links don’t work for the moment. I will complete the demos first.

From the poll, the following features are now ok:

- Several AjaxSearch instances on a page
- Define categories and display the results per category
- Allow $_GET requests for Google Analytics

and Custom output is on track.

Sweet! Nice with $_GET for GA!

I can’t find the link to download on your website? :/ Could you point me in the right direction?

I will add the download link at the end of the week. Before I need to finalize some minors points.

AjaxSearch 1.9.0 beta is available on this page

The release not in preparation is here

Last features added:

==== Custom output (demo here)

&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, use the following placeholders

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

The parameter &tplLayout is now deprecated

The parameter &tplInput is now used to style the ajaxSearch input form


The custom output runs only for the non-ajax mode. I have some issues with the mode ajax.



==== 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 feedbacks with IE, Safari and Chrome are welcome. Uses the ajax demos listed on the left menu

Very excited to see the &parents=`in|notin: ...` option. Thank you!

&minChars error is shown twice in &ajaxSearch=`0`, and none in ajax mode.

Thanks goldsky, for this feedback.

To use the previous form for parents or documents parameter like &parents=`12` instead &parents=`in:12`, you should replace the line 75 of classes/ajaxSearchFilter.class.inc.php:
by

how can i use this for my custom module and custom database?

I’m digging the information in the code.
What is this?

// &resultsPage [int]
// The default behavior is to show the results on the current page, but you may define the results page any way you like. The priority is:
// 1- snippet variable - set in page template like this: [[AjaxSearch? AS_landing=int]]
// where int is the page id number of the page you want your results on
// 2- querystring variable AS_form
// 3- variable set here
// 4- use current page
// This is VERY handy when you want to put the search form in a discrete and/or small place
// on your page - like a side column, but don’t want all your results to show up there!
// Set to results page or leave 0 as default
$cfg[’resultsPage’] = $dcfg[’resultsPage’];