Bugfix for viewing blog posts

What does this MR do?

Fixes a bug from !2001 (merged) that caused blog posts to not be visible.

Note: I moved the entry in the changelog because I think we didn't release !2001 (merged) yet. The bug is not on production.

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

Very

How to test

1. Checkout branch locally
2. Login as foodsaver
3. Go to the blog http://localhost:18080/?page=blog
4. Open any post and check that if can see the content

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) (only on beta)
• 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.

Release notes text in German

added forOnly in beta + 1 deleted label

changed milestone to %Release 'Grapefruit': January 2022

added 6 commits

• 4f0085de...551040ef - 5 commits from branch master
• 61ca4c82 - bugfix in BlogControl

Compare with previous version

approved this merge request

added 6 commits

• 61ca4c82...24d70b20 - 5 commits from branch master
• d7a1be47 - bugfix in BlogControl

Compare with previous version

enabled an automatic merge when the pipeline for d7a1be47 succeeds

merged