vb.org Archive - Miscellaneous Hacks - Discourage Report Abuse

Page 2 of 3

Show 40 post(s) from this thread on one page

vb.org Archive (https://vborg.vbsupport.ru/index.php)

- vBulletin 4.x Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=245)

- - Miscellaneous Hacks - Discourage Report Abuse (https://vborg.vbsupport.ru/showthread.php?t=318874)

tareqbd

06-15-2015 02:48 PM

Hi Mark, is it possible to add a feature like "Maximum report per day by per usergroup"

MarkFL

06-15-2015 03:05 PM

Quote:

Originally Posted by tareqbd (Post 2547889)

Hi Mark, is it possible to add a feature like "Maximum report per day by per usergroup"

I will look into adding that feature soon. :D

MarkFL

06-19-2015 03:24 AM

Update: version 1.6

All moderators will see a "report thread" icon which serves as a link to the report thread. The status of the report thread is shown in the icon's tooltip.

MarkFL

06-23-2015 04:58 AM

Quote:

Originally Posted by tareqbd (Post 2547889)

Hi Mark, is it possible to add a feature like "Maximum report per day by per usergroup"

Update: version 1.7

You may now restrict users by usergroup to a certain number of reports per day. Upon installing or upgrading to this version, a new table is created in your database that serves as a log for reports made by users in the restricted group(s). This table is pruned daily to remove rows that are more than 24 hours old.

MarkFL

07-28-2015 05:26 AM

Update: version 1.8

You may now choose to turn off post reporting altogether for selected forums.
You have the option whether to exempt moderators/administrators from this restriction.
Removed the need to make a manual template edit to your postbit template(s).

akz645

07-29-2015 10:40 PM

Quote:

Originally Posted by MarkFL (Post 2551545)

Update: version 1.8

You may now choose to turn off post reporting altogether for selected forums.
You have the option whether to exempt moderators/administrators from this restriction.
Removed the need to make a manual template edit to your postbit template(s).

Cheers Mark :)

akz645

09-04-2015 07:34 PM

Quote:

Originally Posted by MarkFL (Post 2546782)

...

I recently tried this Mod out on my test forum and it made an entire thread no longer accessible (when this Mod is enabled), if it has a single reported post in it (with the error shown below).
Furthermore, after reporting any post, this error message shows up:
Fatal error: Call to a member function fetch_array() on a non-object in /home/[My DB]/public_html/includes/class_postbit.php(345) : eval()'d code on line 287https://vborg.vbsupport.ru/external/2015/09/28.png
--------------------
Report Thread Prefix Management + Profile Reporter => Those Mods seem to work though.
Mark, can you take a look at my forum? Should I PM you the details?

It probably does clash with another modification, but I'm not sure which. If we could order modifications based on the date they were installed, that would made it so much easier to unistall them in order to find the problem/conflict.

MarkFL

09-04-2015 09:10 PM

First, let's try this...at the top of the plugin titled "Discourage User From Reporting Post More Than Once", add the following code in red.

Code:

if ($vbulletin->options['markfl_pdpr_enabled'])

{

        global $db;

        $reported = false;

        $report_again = false;

Let me know if that fixes the problem on your end. :)

akz645

09-04-2015 09:19 PM

Quote:

Originally Posted by MarkFL (Post 2554297)

First, let's try this...at the top of the plugin titled "Discourage User From Reporting Post More Than Once", add the following code in red.

Code:

if ($vbulletin->options['markfl_pdpr_enabled'])

{

        global $db;

        $reported = false;

        $report_again = false;

Let me know if that fixes the problem on your end. :)

Cheers that fixed the problem :)

Can you explain to me why it fixed the issue?

MarkFL

09-04-2015 09:25 PM

I run into this error occasionally with the fetch_array() function, but only at certian hook locations which can be different on other sites, and I have found that making $db global is the cure. Why this needs to be done for some sites and not others I have no clue, but I think I will start including that statement in every plugin that uses the fetch_array() function from now on just to make sure everyone is covered. :)

All times are GMT. The time now is 10:38 AM.

Page 2 of 3

Show 40 post(s) from this thread on one page

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01011 seconds Memory Usage 1,740KB Queries Executed 10 (?)
More Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (2)bbcode_code_printable (5)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)pagenav (1)pagenav_curpage (2)pagenav_pagelink (1)post_thanks_navbar_search (1)printthread (10)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start pagenav_page pagenav_complete bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages: