Using Ajaxsearch as a 'simple' search?

How would I accomplish the following:

I’d like to put a search box on every page, but without the Ajax behavior... basically just an input field
with a ’search’ submit button that passes its value to a new page that will have the search results.


Darkelve78

You find it all in the readme-file.

&ajaxSearch [1 | 0] (optional)
        Use the ajaxSearch mode. Default is 1 (true)
        The AjaxSearch mode use an Ajax call to get the results without full page reloading

See the Wiki also. (Not for 1.8.0 but very up to date on the basics).

Yeah, I found that already. I guess my real question is, if I create a page containing an AjaxSearch ’noninteractive’ call, then how do pass the parameter from one page (input field) to the other (AjaxSearch)?

I want the search box on all pages, but the results to show in a new page.

Edit: Woops! I found out how to do it... in the example code, I gave in an existing page id for the example, so it looked like no new page was being opened... x)

It works now, but I get the search result 2 times if I do it like in the documentation? But it does work as expected when I just use an ’empty’ page as a landingpage. Does need a new template though

You don’t need another template for the landing-document (the document to show the search result).

For example, put
in your template to gt the search box on all your pages.

Then put i.e.
in your landing document.

This way the only place you get the search results is in your landing document. With the same template as all your other documents. 

When I develop I usually create a couple of text TVs and place them before and after the content placeholder in the template. The I assign these TVs to a private manager group so that I can issolate them from other managers. Then I use these for adding elements to a page that I don’t want the normal managers to edit, like specifi calls to stuff like ajaxsearch or ditto or anything that I want to add that is not to be edited. Beats having to create a new template.

Ends up looking like this in the template:
[*pre_content*]
[*content*]
[*post_content*]

This really helps to keep snippet calls away from the clients reach

@Sylvaticus: thanks, this is what I was looking for!

@dev_cw : great advice