Conversation
supportDo you have a FAQ entry which answers this? Also at https://feedbackwp.com/docs/ i do not see it. But it should not be needed to access such page to learn how to do it. I have expected some section where i can see the list of feedback and delete these or click to edit post. “Stats” named page shows stats, but not feedback text, allowing to quickly cleanup it, avoiding too much content in database.
Hi 👋🏽, Feedback text submitted by users is displayed in the Feedback metabox inside the post editor. Open the post that received feedback in the WordPress editor and look for the Feedback section in the sidebar or below the content area. The submitted responses will be listed there. To find all posts with feedback or ratings, go to Feedback WP > Stats in your WordPress admin. Hope that helps!
Hi, you have described current state, which seems to me as a insufficient state/approach, because of what I have mentioned: “Stats” named page shows stats, but not feedback text, allowing to quickly cleanup it, avoiding too much content in database. Stats page does not even show a date to better understand which feedback is new. No way to delete/cleanup solved feedback. The feedback text should be listed right on the page so user does not need to spend time and resources to load editor to read each of the feedbacks while some can be spam that could be deleted in one second using single click from the currently non-existing list of feedbacks. Beside delete action, user could be able to mark read/unread and the “Stats” tab (maybe not appropriate name) should contain a red icon with a count of number of unread feedbacks to draw admin attention while he is on a different page of wp-admin. I wanted to ask you to un-mark this as resolved and consider it as a feature request for adding to your possible todo list please.
Hi, Fair points. You’re right that the Stats page doesn’t show the actual feedback text or let you delete and triage from the page. I’ve noted your suggestions for the team: a feedback list with the text and dates, delete, read/unread, and an unread count. Can’t promise when, but it’s added to the to-do list as a feature request. Keeping this marked resolved since it answers the original question, but the feature request is noted. Best regards
Hi 👋🏽, Feedback text submitted by users is displayed in the Feedback metabox inside the post editor. Open the post that received feedback in the WordPress editor and look for the Feedback section in the sidebar or below the content area. The submitted responses will be listed there. To find all posts with feedback or ratings, go to Feedback WP > Stats in your WordPress admin. Hope that helps!
Hi, you have described current state, which seems to me as a insufficient state/approach, because of what I have mentioned: “Stats” named page shows stats, but not feedback text, allowing to quickly cleanup it, avoiding too much content in database. Stats page does not even show a date to better understand which feedback is new. No way to delete/cleanup solved feedback. The feedback text should be listed right on the page so user does not need to spend time and resources to load editor to read each of the feedbacks while some can be spam that could be deleted in one second using single click from the currently non-existing list of feedbacks. Beside delete action, user could be able to mark read/unread and the “Stats” tab (maybe not appropriate name) should contain a red icon with a count of number of unread feedbacks to draw admin attention while he is on a different page of wp-admin. I wanted to ask you to un-mark this as resolved and consider it as a feature request for adding to your possible todo list please.
Hi, Fair points. You’re right that the Stats page doesn’t show the actual feedback text or let you delete and triage from the page. I’ve noted your suggestions for the team: a feedback list with the text and dates, delete, read/unread, and an unread count. Can’t promise when, but it’s added to the to-do list as a feature request. Keeping this marked resolved since it answers the original question, but the feature request is noted. Best regards