Discourse 사용자 피드백

커뮤니티 구성원들이 서로에게 리뷰와 평가를 할 수 있도록 하고 싶으신가요? 이제 이 기능을 커뮤니티에 활성화할 수 있습니다!

개요

Discourse User Feedbacks 플러그인은 각 사용자가 다른 커뮤니티 구성원에게 평가와 피드백을 남길 수 있도록 합니다.

각 사용자는 관리자(Admin)를 포함한 다른 커뮤니티 구성원에게 피드백을 남길 수 있습니다.

이 기능은 다른 사용자에 대한 청중의 의견을 이해하는 데 도움이 되는 커뮤니티에 유용합니다.

Marketplace 유형의 서비스를 제공하는 커뮤니티 등에 유용합니다.

사용자는 사용자 프로필피드백을 방문하여 다른 사용자에게 피드백을 남길 수 있습니다.

사이트 설정에 따라 평균 평가는 사용자 카드, 게시물의 작성자 사용자 이름 옆, 사용자의 프로필 페이지에 표시될 수 있습니다.

사용자 프로필

사용자 카드

게시물 내 사용자 이름 옆

설정

:link: 저장소 링크

:link: 플러그인 설치 방법

구성

다음 사이트 설정을 구성할 수 있습니다:

  • user feedbacks enabled 플러그인을 활성화합니다.
  • user feedbacks allow reviews 사용자가 다른 사용자의 의견을 제공할 수 있도록 허용합니다.
  • user feedbacks display average ratings beside username on post 사용자의 모든 게시물에서 사용자 이름 옆에 평균 사용자 평가를 표시합니다.
  • user feedbacks display average ratings on profile 사용자의 프로필에 평균 사용자 평가를 표시합니다.
  • user feedbacks display average ratings on user card 사용자 카드에 평균 사용자 평가를 표시합니다.
  • user feedbacks hide feedbacks from user 비관리자 사용자에게 피드백을 숨깁니다

:warning: 공지

라이브 포럼에서 사용하기 전에 플러그인을 테스트해 주세요.

29개의 좋아요

Loving this. Any chance to become official? :pray:

6개의 좋아요

I can’t say anything on this It totally depends on the @team if they want to takeover or not.

4개의 좋아요

I have added a feature to anonymize user feedbacks:

  • Only admins will be able to view the ratings + reviews any user got from their fellow members.
  • Normal User can just see their rating for anyone else.
  • Average ratings will be visible to everyone.

This can solve the issue of the rating war between the users and will anonymize the identity of the user who gives feedback.

Please update the plugin and enable the user_feedbacks_hide_feedbacks_from_user setting.

3개의 좋아요

Great plugin as always from Ahmed.

For marketplace type services the plugin should have a restrict to group feature where only set group members can receive reviews.

3개의 좋아요

Thanks @Mr.X_Mr.X

That’s correct, but it will be applicable to only those forums who have restricted Marketplace category to any groups. I haven’t seen any forum with this, but if there’s some user’s who need this, I will add this to the plugin.

3개의 좋아요

Hello! I love what you made. I don’t see a license in the Github repo though, what usage is okay?

3개의 좋아요

Thanks @Ocarune
It comes under MIT license, I’ll add the license in some time, thanks for the reminder though!

3개의 좋아요

Thank you so much! :slight_smile:

3개의 좋아요

Thank you!

Have you considered a dedicated fieldn for a internal reference? This could be used to link to the topic where the item was sold, or simular thing.

1개의 좋아요

I’ll bump this just to hear if @Ahmed_Gagan had any thoughts on this?

I would also like to suggest that ${count} has three strings, instead of a single one.

  • No feedback
  • 1 feedback
  • More than 1 feedback

Also, yet another thing:
It would make great sense to have “toggle” on where to show the rating. Let’s say I have the categories called: “I would like to buy X” and " I would like to sell Y". Here I would like to mark these two categories, so rating would be shown in these next to the user, but not in all other categories out of context.

I would also like to hear a bit about how you’re thinking the moderators should delete any feedback(s) which are unwanted? :slight_smile:

Again; Thank you for making this. :partying_face: !


TL;DR would be:

It would be great to see the following improvements:

  • Link-field to internal reference
  • Add “Display average user rating in specific categories
  • Add wordings for zero, one or many feedback(s)
2개의 좋아요

Glad to see someone open source this

1개의 좋아요

Hi @Ahmed_Gagan

It’s sadly breaking a native Discourse function:
https://meta.discourse.org/t/cant-get-who-liked-a-post-post-action-type-id-2-returns-error-500/223800/2?u=exetico

Are you aware of it? I’m also wondering how a plugin are able to break a native Discourse route.

1개의 좋아요

Hi @exetico

I saw a similar functionality in swapd.co forum, but I didn’t got time to add it to the plugin yet. It’s in my roadmap.

I’ll update you once I add this feature to the plugin.

Sounds good to me, but we can allow tl4+admins+moderators to delete irrelevant feedbacks.

Thanks for reporting, I’ll add all 3 options.

Sounds a nice feature, I’ll add a setting where admins can select category where they want to show the ratings.

Thanks for reporting the bug, I’ll add a fix by tomorrow.

Thanks for using the plugin mate :blush:

5개의 좋아요

Hi,

Thank you for the great response. How is it going with both the bug, and the improvements? :clap: :blush:

Is it moving forward?

No changes is found in the repo, but I’d like to ask anyways :slight_smile:

https://github.com/Ahmedgagan/discourse-user-feedbacks

1개의 좋아요

Hey @exetico
I am on a trip from last 20 days, will fix it in next 5-6 days

The endpoint which normally returns who liked a post is returning error 500 on our forum.

GET Request:

https://domain.com/post_action_users?id=512345&post_action_type_id=2

Response:

{"status":500,"error":"Internal Server Error"}

We’re rocking:

2.9.0.beta3 (be519d2aec)

By using the “Data Explorer” plugin, our “like”-details is found as expected.

So I’m now wondering if there’s a problem with the latest version?

1개의 좋아요

It’s sadly related to:

Rails log

Started GET "/post_action_users?id= 512345&post_action_type_id=2" for <clientIp> at 2022-04-09 16:57:10 +0000
Processing by PostActionUsersController#index as JSON
  Parameters: {"id"=>"512345", "post_action_type_id"=>"2"}
Completed 500 Internal Server Error in 23ms (ActiveRecord: 0.0ms | Allocations: 8877)
NoMethodError (undefined method `feedbacks' for nil:NilClass)
(eval):12:in `_fast_attributes'
app/controllers/application_controller.rb:497:in `serialize_data'
app/controllers/post_action_users_controller.rb:41:in `index'
app/controllers/application_controller.rb:400:in `block in with_resolved_locale'
app/controllers/application_controller.rb:400:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:71:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:358:in `call'
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/enforce_hostname.rb:23:in `call'
lib/middleware/request_tracker.rb:202:in `call'

So not related to anything in the main solution.

I’ll jump to the other thread dedicated to the plugin.

3개의 좋아요

Hi @exetico :slight_smile: I’ve moved your bug report over to the relevant plugin topic to hopefully get it in front of the right people. :crossed_fingers:

Edit: Though it seems I did not read it closely enough, and you have already done a similar thing. My apologies for the noise @Ahmed_Gagan :pray:

4개의 좋아요