Sorry - we fixed the db error when searching just after it being reported.
The other issues should have been resolved too.

Again, sorry!