Fix nightly fetcher warnings by using expected id instead of betrieb_id allowing all nightly maintenance methods to be executed again
Touches #747 (closed)
What does this MR do?
After deploying #747 (closed) to production during our january release we broke the nightly maintainance scripts which stopped directly at the beginning after access to an array id was wrong. This got fixed directly on the server via ssh and is running fine since. This MR brings this change to master so it can move to production as a real fix soon/later.
How confident are you it won't break things if deployed?
Very - as it is already on the live server
Links
Any relevant links (issues, documentation, slack discussions).
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
joined #foodsharing-beta channel at https://slackin.yunity.org -
added an entry to CHANGELOG.md (description, merge request link, username(s)) -
Once your MR has been merged, you are responsible to update the #foodsharing-beta Slack channel about what has been changed here. They will test your work in different browsers, roles or other settings
Edited by Johannes