Fix the user search pointing to a non-existing path
What does this MR do?
Fixes errors like No route found for "GET /api/search/legacyindex
that come up since !2115 (merged) on the message page.
How confident are you it won't break things if deployed?
Very
How to test
- Checkout branch locally
- Login as foodsaver
- Open the developer console
- Go to the "all messages" page http://localhost:18080/?page=msg
- Check that there is no "404 /api/search/legacyindex" but a "200 /api/search/index" instead
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
set a "for:" label to indicate who will be affected by this change -
used "state:" labels to track this MR's state until it was beta tested -
added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) -
added an entry to CHANGELOG.md
-
added a short text that can be used in the release notes -
Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".- Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
- Be aware, that also non technical people should understand.