Searching for commas & spaces alone yields Server Error

[gitname]

When I search for a string consisting of only spaces, by entering those spaces (encoded as %20s) directly into the address bar, the Grav Blog Skeleton demo site shows a "Server Error" page. This is shown in the Experiment C section below.

---

Experiment A. Search for non-whitespace characters, using search form:

I get a "0 results" message. I consider this to be the "by design" behavior.

Link: https://demo.getgrav.org/blog-skeleton/search/query:test

---

Experiment B. Search for whitespace characters only (i.e. 4 spaces, entered as ), using search form:

I get an "Error 404" page.

Link: https://demo.getgrav.org/blog-skeleton/search/query:

---

Experiment C: Search for whitespace characters only (i.e. 4 spaces, encoded as %20%20%20%20), using address bar:

I get a "Server Error" page containing information about the PHP code in use.

Link: https://demo.getgrav.org/blog-skeleton/search/query:%20%20%20%20

[gitname]

Experiment D: I see the same Server Error page when I search for a lone comma (i.e. ,).

Link: https://demo.getgrav.org/blog-skeleton/search/query:,

To demonstrate that this is not limited to searches performed by directly manipulating the URL; entering 2 spaces and a comma (i.e. ,) in the search form in the Blog Skeleton demo site yields the same result (the client-side validation prohibits submission of a comma alone).

---

I think, as long as the search box contains only commas, only spaces, or only commas and spaces, this error will occur.

[gitname]

I see the same behavior on a site I am developing. On that site, I am running Grav v1.1.5, Admin v1.2.2, and SimpleSearch v1.9.2.

[coyoterj]

Hi,
When doing a search with comma at the end ( teste, ), this error occur:

[flaviocopes]

Should be fixed now, if you can test @coyoterj @gitname

[flaviocopes]

(not yet released, but in develop)

[coyoterj]

Hi @flaviocopes,

Tried to "bin/gpm update simplesearch", results:
"GPM Releases Configuration: Stable

Nothing to update."

Then, I updated the file simplesearch.php and that worked perfectly. ;)

Thanks!