Bug in the search form

[iliion]

This is probably a Bug related to this feature and the strange behaviour is caused after this commit.

---

Explanation

In essence the above feature #253 will work only if the landing page (aka. the root catalog) contains the following link:

{
      "rel": "data",
      "type": "application/json",
      "href": <base_url_here> + "/collections",
      "method": "GET"
}

In case this link is not present then it is not possible to insert a collection manualy into the search form. Basically I insert a collection in the Collections text area and I press enter and then it appears in the Item IDs area (see screenshot).

I think the aforementioned feature is very useful and I was wondering if its possible to decouple its functionality from the fact that we need to keep a "data" link in the root catalog.

---

Note: Related issue

[m-mohr]

Sure, that's a bug, I'll fix that. Thanks for reporting.

[m-mohr]

Please try again :-)

[iliion]

It is resolved. Thanks a lot @m-mohr

[iliion]

Hi @m-mohr .It is true that now a user can insert a collection but the collections argument in the query string remains empty. I hadnt noticed it last night .

ex.: http://<host>/search?limit=12&collections=

Debug screenshot:

[m-mohr]

I didn't had an API at hand yesterday that didn't had collections so this was somewhat a "blind" bug fix, but found one now so was able to actually check what's going on and it's fixed now as far as I can tell (at least it works for EarthSearch).

[iliion]

It works fine :). I can confirm that