Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reported content: send notifications to admins when someone reports content (Trac #3252) #3252

Closed
elgg-gitbot opened this issue Feb 16, 2013 · 9 comments · Fixed by #13891
Closed

Comments

@elgg-gitbot
Copy link

Original ticket http://trac.elgg.org/ticket/3252 on 41236133-11-25 by cash, assigned to unknown.

Elgg version: Github Master

The reported contented plugin is used to report users who are spamming, trolling, or just being difficult. It is also used by users to report problems with a site. Currently, the only way an administrator knows about the reports is to login to the admin area and check.

Instead, when a report is created a notification should be sent to the admin (or admins) of the site. There should also be a plugin setting for turning this off.

@elgg-gitbot
Copy link
Author

trac user soniea wrote on 41242361-04-23

Notifications will be sent with this patch.
Plugin setting option yet to be added.

@elgg-gitbot
Copy link
Author

trac user hellekin wrote on 41273299-10-25

I see 3 issues with this patch:

  • no gatekeeper
  • forward() could be used only once
  • tabs (according to Elgg Coding Standard, one should use 4-space-equivalent tab characters)

any update?

@elgg-gitbot
Copy link
Author

ewinslow wrote on 41273966-01-15

Gatekeepers are not needed in actions. The action handler adds them automatically.

@elgg-gitbot
Copy link
Author

Attachment added by trac user soniea on 41293866-11-08: add.php

@elgg-gitbot
Copy link
Author

Attachment added by trac user soniea on 41293869-05-10: edit.php

@elgg-gitbot
Copy link
Author

trac user soniea wrote on 41293873-08-08

Plugin setting to enable or disable email/message notification has been added.
It needs to be put in mod/reportedcontent/views/default/settings/reportedcontent

Regression test on reportedcontent passed.

@elgg-gitbot
Copy link
Author

brettp wrote on 41293934-01-02

Soniea - Trac tickets are only resolved as "Fixed" when we commit the code. Can you please provide a patch against the latest trunk or send a pull request on github?

@elgg-gitbot
Copy link
Author

cash wrote on 41296526-01-29

Sunithi - thanks for the files. A few comments:

  • There are some coding standards issues with spaces vs tabs and spacing of statements. See the coding standard in the root directory
  • You should not need the echo ' ' in the edit settings view
  • There is a new function in Elgg 1.8 for grabbing admin users so that you don't need to write SQL (something like elgg_get_admins())
  • You need to pull some of the strings from the notifications out and run them through elgg_echo().

@elgg-gitbot
Copy link
Author

trac user soniea wrote on 41297060-01-13

I've reused edit.php from logrotate with slight modifications.So i'm guessing we need to take care of the echo messages there as well.
Will implement the elgg_get_admins().
I didn't know we had that :D

Please find the interim fix at github.com/soniea/Elgg

@ewinslow ewinslow added the spam label Apr 18, 2014
@jdalsem jdalsem added this to the Elgg 4.1 milestone Feb 2, 2021
jeabakker added a commit to jeabakker/Elgg that referenced this issue Jan 26, 2022
jeabakker added a commit to jeabakker/Elgg that referenced this issue Jan 26, 2022
jeabakker added a commit to jeabakker/Elgg that referenced this issue Jan 26, 2022
jeabakker added a commit to jeabakker/Elgg that referenced this issue Jan 26, 2022
jeabakker added a commit to jeabakker/Elgg that referenced this issue Jan 26, 2022
jeabakker added a commit to jeabakker/Elgg that referenced this issue Jan 26, 2022
jeabakker added a commit to jeabakker/Elgg that referenced this issue Jan 26, 2022
jeabakker added a commit to jeabakker/Elgg that referenced this issue Jan 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants