Not a bug Search accepts invalid prefixes without error

Kirby

Well-known member
Affected version
2.1.7

This URL contains the invalid prefix "invalid"

Expected Result
Some kind of error

Actual Result
Search is perfomed on the keyword only

This seems inconsistent, as specifying an invalid int value like 9999 does produce an error No results found
 
I don't think we're planning to change anything here. This expects an integer input so that value is cast to 0. 0 has the meaning of any prefix and thus we don't apply a constraint.

This behavior of input casting is something that is generally applied consistently through XF.
 
Back
Top Bottom