PROD-31065: [IOSA-SUP] Reported content cannot be seen or deleted from the Report Overview Page #4219
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem (for internal)
Reported content cannot be seen or deleted from the Report Overview Page by a Site Admin role. Please see the attachment, there is no option to delete and also when clicked on the view comment it doesn't direct to the comment, the user stays at the page. If we try to delete the reported content from the post itself, it gives the following message and do not delete. {"message":"The "comment" parameter was not converted for the path "/ajax_comments/{comment}/delete" (route name: "ajax_comments.delete")"} Reported contents can only be deleted from content overview page.
Solution (for internal)
Rework the reports page to add a delete option, filters and fix errors on the view action.
The destination parameter was removed from action links because it breaks a redirect that exists on routes.
Release notes (to customers)
The Reports page (/admin/content/reports) was updated, direct link to remove content and filters by type and status were added.
Issue tracker
https://getopensocial.atlassian.net/browse/PROD-31065
Theme issue tracker
How to test
There was another PR #4190 that was declined because the update path was not provided, the only difference now is hook update, so we need to check only this.
Change Record
Translations