fix orga foodsaver report post
closes #1764 (closed)
What does this MR do?
In production the table is fs_fsreport_has_wall_post -> it is the wallpost to reports from a foodsaver #1764 (closed) reverts mostly changes from !2770 (merged)
How confident are you it won't break things if deployed?
???
Links to related issues
How to test
In Prod the table is fs_fsreport_has_wallpost - I don't know if at some point the table got renamed in prod or in dev - but all dev scripts state it as fs_reports_has_wallpost - but that would intend another content.
rename table fs_report_has_wall_post to fs_fsreports_has_wallpost
- Checkout branch locally
- Login as userorga
- go to Göttingen - optioned
- enable report support
- choose a profile and write a report
- go to profile and open report
- you should see the list of reports and the wallpost underneath. -->
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.
Edited by -