vb.org Archive - Administrative and Maintenance Tools - SSGTI

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

- vBulletin 3.8 Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=235)

- - Administrative and Maintenance Tools - SSGTI - Auto Ban Under Age Users (https://vborg.vbsupport.ru/showthread.php?t=219138)

Quote:

Originally Posted by esperone (Post 1854082)

wow. nice work.

Thanks. :up:

Quote:

Originally Posted by Med (Post 1854164)

Very nice Thx

You Are Welcome :).

Quote:

Originally Posted by Alfa1 (Post 1855433)

Thank you for publicly releasing it.

My Pleasure ;).

Quote:

Originally Posted by Konstantinos (Post 1855801)

good idea, but can u aslo add a function that when the ban occurs a thread to be created to forum for the reported posts ? so the admins can know fast who is the underaged person

edit

i run the task mannually after install and got

Ban Under Age Users

Warning: mktime() expects parameter 6 to be long, string given in [path]/includes/cron/ssgti_banunderage.php on line 42

Warning: mktime() expects parameter 4 to be long, string given in [path]/includes/cron/ssgti_banunderage.php on line 42

Warning: mktime() expects parameter 4 to be long, string given in [path]/includes/cron/ssgti_banunderage.php on line 42

Hmmmmmm, really I didn't understand your idea or may be vise-versa! :)
The product's main functionality is to ban under age users automatically, so what do you mean by:

Quote:

aslo add a function that when the ban occurs a thread to be created to forum for the reported posts

Any way, regarding to the error that you've got: I can't re-produce it neither on my local machine nor on any of my testing servers. But it's under investigation currently. A fix will be available soon.

Quote:

Originally Posted by Alfa1 (Post 1862815)

My errors are similar. Does anyone have this working?

In fact it's working 100% on my local machine & all of my testing servers. I don't know why that happens with you, but don't worry. It's under investigation currently. A fix will be available soon.

The problem has been solved & all issues has been fixed in a new version. It will be published soon (tomorrow).
The new version includes a number of optimizations & some new features such as "email banned users" & "excluding some user groups" from being auto banned.

You will like that new version, I'm sure :).

Upgrade: Highly Recommended.

v3.8.110 29/09/2009 01:00 AM UTC: Second public release (Fixes/Optimizations/New Features).
- Changes:
  - Many code optimizations.
  - Fixing "mktime" issues.
  - Exclude staff members (moderators/super moderators/administrators) by default from being auto banned.
  - The product will stop if the staff member responsible for banning is invalid.
- New Features:
  - If you run the cron job manually from AdminCP, you will get a simple report of banned users.
  - Now you can exclude some user groups from being auto banned by this product.
  - Now you can auto send emails as notifications to all auto banned users.

With the new version, I get this:

Quote:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 45 bytes) in /forum/includes/class_core.php on line 3259

I currently have 435 underage members, and about 80.000 userid's.

Quote:

Originally Posted by Alfa1 (Post 1893537)

With the new version, I get this:

I currently have 435 underage members, and about 80.000 userid's.

Oh, that's because of your large number of banned users. The processing cycle multiplied by that number of banned users seems to be heavy. Try this solution currently ...
Please put the following line of code at the begin of your cronjob file "includes/cron/ssgti_banunderage.php":

PHP Code:

ini_set("memory_limit", "128M");

Then run the scheduled task again & tell me what happens.

Almost the same error:

Quote:

SSGTI - Ban Under Age Users
ini_set("memory_limit", "128M");
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 43 bytes) in /forum/includes/class_core.php on line 3257

I assume this is because I have set the memory_limit to 64mb in .htaccess, so that this is not reverted with server upgrades. I have temporarily set my memory limit to 128MB, then ran the cron without errors and then lowered it back to 64MB.

But the 435 underage members are not banned by the cron.

Quote:

Originally Posted by Alfa1 (Post 1894128)

Almost the same error:I assume this is because I have set the memory_limit to 64mb in .htaccess, so that this is not reverted with server upgrades. I have temporarily set my memory limit to 128MB, then ran the cron without errors and then lowered it back to 64MB.

Sounds Good, that means it works fine with this solution.
A better solution may be available if possible, since the processing cycle already requires the same amount of overhead & it's approximately the same as default vBulletin ban process. The difference is the loop in which multiple users are to be processed respectively.

Quote:

Originally Posted by Alfa1 (Post 1894128)

But the 435 underage members are not banned by the cron.

What do you mean exactly!? Since the cron has been executed successfully, then it should do it's work!
Can you answer please on the following questions:
When you run the cronjob manually from AdminCP, what did you get? Did you get a report with banned users, or may be you get only a phrase saying "Done" without any listed users?

Do you've already underage users that aren't already banned before?

The "already banned" users, when there ban will be lifted?

I do not get a report. Just a note that the process is done, without any list of banned members.
I have 435 underage members that the system still needs to ban.
I have 210 banned members that are underage. These have been banned manually and the time span within which their ban will be lifted ranges from 1 month to 2 years or never.

Quote:

Originally Posted by Alfa1 (Post 1895372)

I do not get a report. Just a note that the process is done, without any list of banned members.
I have 435 underage members that the system still needs to ban.
I have 210 banned members that are underage. These have been banned manually and the time span within which their ban will be lifted ranges from 1 month to 2 years or never.

This is absolutely strange & unexpected behavior.
The product supposed to do it's work without any problems at this point.
I'm sure it isn't something related to the product's code itself, may be some settings configured wrong.
If you wish me to investigate that problem, please send me (via PM) a temp forum admin that has permissions to control settings & scheduled tasks. If you can demonstrate/reproduce the same problem on a demo board, it's OK; you can supply access to that demo board not the live one.

new ver doesnt work either, it doest ban and settings are correct

X vBulletin 3.8.12 by vBS Debug Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (1)bbcode_php_printable (12)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:

Phrase Groups Available:

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01123 seconds Memory Usage 1,761KB 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 (1)bbcode_php_printable (12)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: