Don't use startPage

I am not sure you are referring to the result provided from the module, or from the search module.

You are referring to /search/node/Query?page=1, which is the relative path used by search.module.

Hi Kiam,

after you add the opensearch provider to firefox, you can search the drupal site using the browser's top right box (in my case).

This box submits to /search/node/Query?page=1 (which is Page 2 in Drupal)

So I think the browser adds this "1". I removed the page={startPage}, so it submits to /search/node/Query, without a "page=1". Seems unecessary.

So change:

url('search/' . $info->type . '/{searchTerms}', array('query' => 'page={startPage}', 'absolute' => TRUE))

to:

url('search/' . $info->type . '/{searchTerms}', array('absolute' => TRUE))

It think that is the way to do it. I don't see why the browser-search should set the page=x.

It think that is the way to do it. I don't see why the browser-search should set the page=x.

That is necessary for the other pages. A search could return more than one page of results; without that parameter, you would always see the first page.

I got it; if startPage is used, the search engine will always ask for page #1, which is the second results page for Drupal.
I removed the parameter startPage, even if I could have used page={startPage?}, which would have made that parameter optional. I noticed that Firefox doesn't pass such parameter for any of the search engines it currently defines (including Wikipedia, that is added to Firefox through an Opensearch description file returned from wikipedia.org).

I changed the code, and committed it. Thanks for your report, and help.