QuickSearch improve error checking

[ClayBirkett]

website was crashing from bot use of quicksearch
fixed a few problems

Checklist

• Refactoring only
• Documentation only
• Fixture update only
• Bug fix
  • The relevant issue has been closed.
  • Further work is required.
• New feature
  • Relevant tests have been created and run.
  • Data was added to the fixture
    • Data was added via a patch in /t/data/fixture/patches/.
  • User-Facing Change
    • The user manual in /docs has been updated.
  • Any new Perl has been documented using perldoc.
  • Any new JavaScript has been documented using JSDoc.
  • Any new legacy JavaScript has been moved from /js to /js/source/legacy.

[ryan-preble]

I have often used both eval and Try::Tiny to do error handling, but I hear that Try::Tiny is better. Should we commit to using one or the other for new code or does it not matter? Does Perl wizard Lukas have any input?

[lukasmueller]

I have often used both eval and Try::Tiny to do error handling, but I hear that Try::Tiny is better. Should we commit to using one or the other for new code or does it not matter? Does Perl wizard Lukas have any input?

Try::Tiny is just syntactic sugar on an eval, as far as I know. So they two should be equivalent, but Try::Tiny is a bit easier on the eyes, so potentially we should prefer it for that reason.

[lukasmueller]

Maybe the quick search should be behind a login? User configurable in sgn_local.conf?