follow up for store controller

#1860 (closed)

What does this MR do?

How confident are you it won't break things if deployed?

Links to related issues

How to test

Screenshots (if applicable)

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
• 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 in the release notes to /release-notes/YYYY-MM.md
• Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/region?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.

added 1 commit

• 959f31f5 - fix title for other user

Compare with previous version

added 41 commits

• 959f31f5...1f20552d - 40 commits from branch master
• 24d9fa7e - Merge branch 'master' into store-controller-follow-up

Compare with previous version

added 1 commit

• 03d862f3 - CHANGELOG.md

Compare with previous version

marked this merge request as ready

marked the checklist item added an entry to CHANGELOG.md as completed

changed milestone to %Release "Laugenbrezel"

marked the checklist item added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) as completed

added forOrga only label

removed forOrga only label

added forOnly in beta label

marked the checklist item set a "for:" label to indicate who will be affected by this change as completed

approved this merge request

merged