Hello everyone, this is Submit Antispam Addon module.
Most of you are bored of never ending spam. This module can solve your spam problems at 99%. Forever.

This module allows create user authorizations to submit certain number of new stories/comments based on quality of recent user submissions.

It means there is a restriction policy for submitting new stories:

• Level 0 Authorization = (default) user authorization, user can submit 1 story per day
• Level 1 Authorization = user authorization, user can submit x stories per day
• Level 2 Authorization = user authorization, user can submit y stories per day
• Level 3 Authorization = user authorization, user can submit z stories per day

How many links can be submitted, average user link votes count required to get certain level of autorization,enabling comment restriction policy and modifying comment multipler - all of these can be done after installing in Admin page in Pligg Configuration section, specificly Submit AntiSpam Addon category.

How it works:
It is pretty simple - when user reach submission limit then they will not be able to submit next story/comment in following 24 hours. See attached pictures.

Installation:
Download submit_antispam.zip archive, unpack and copy to your Pligg Modules folder.

1) open submit_step_3.tpl (located in templates/template folder) and at the end after "</fieldset>" tag add:

{checkActionsTpl location="tpl_submit_step_3_end"}

2) if you want to use comment restriction as well (default value is true) open story.php in root folder and into function insert_comment() before require_once(mnminclude.'comment.php') add:

    check_actions('story_insert_comment',$vars);

Now you can install this module in Modules option in admin panel.
Compatibility note: This module was developed on 9.7 version but it was successfully tested on 9.9 version of Pligg.

Module language can be changed in lang.conf file, styles in css file. Javascript file is not supposed to be changed until you are pretty sure what you do.

Module configuration:
This is Alfa and Omega of this module. There is no general option how configure this module to work on all sites. Only you know what are your users and how strict restrictions should be. Let´s see individual settings which can be customized in Submit Antispam Addon:

• links history count
• level 1-3 user authorization
• level 1-3 allowed links count
• enable comment restriction
• comment submission multiplier

Links history Count
How many latest user links are evaluated when average user links votes value is calculated - in the other words this is "retrospective settings". It can be set for links and comments the same value only.

[Tip - if you want to distinct value for comments, open submit_antispam_main.php and change:]

$average_u_c_v=$db->get_var("SELECT avg(comment_votes) FROM ". table_comments . 
" WHERE comment_user_id=$current_user->user_id LIMIT $links_history_count");

Level 1-3 user authorization
Define average user links votes value required to become Level 1..2...3 user. Higher value = higher restriction. Each of levels can be set to desired value.

Level 1-3 Allowed links count
Define how many links are allowed to submit for user with Level 1-3 authorization in 24hrs.

[Tip - If you want to customize Level 0 value open submit_antispam_main.php and change]

    switch ($authorization_submit_level) {
             case 0:
             $submit_limit = 1;

Enable comment restriction
Define if comment submission restriction policy is enabled or not.There is really nothing special about this settings, just set true for enabling or false for disabling it.

Comment submission multiplier
Define how many comments are allowed at current authorization level x multiplier. To more understand that, you have to understand how comment votes limit value is calculated:

comments_limit = submit link limit * submit_multiplier * average user comments value;
submit link limit - depends on current user authorization level
submit_multiplier - multiply the whole equation
average user comments value - multiply the whole equation (it is calculated and cannot be edited)

You can also watch attached comment image.

What else to know: Countdown timer is done by javascript, it is not static value.

Update 0.15:
+ fixed bug for administrators submissions
+ fixed average user votes count bug
+ everything in language file now
+ optimized sql code

[danwalsh]

Brilliant Module AnAlienHolokres, thanks.

like Sach4isha i'd like to limit to one per hour, is it possible to change a 1/24 day anywhere?

many thanks

dan

[crazyleaf]

Does anyone use this mod in 9.9.5 ?

For me, on 9.9.5, when a new user posts a new story it gets this error :

Warning: strtotime() [function.strtotime]: Called with an empty time parameter. in /home/zabox/public_html/modules/submit_antispam/submit_antispam_main.php on line 96

What can I do ?

[crazyleaf]

Nobody got this problem on 9.9.5 ?

[paulocon]

Hi,

Anyone know any way of disabling the criteria for certain 'trusted' users?
I have a few users which submit quality content on a regular basis and would like them to submit as much as they want..

[AnAlienHolakres3]

Originally Posted by paulocon

Hi,

Anyone know any way of disabling the criteria for certain 'trusted' users?
I have a few users which submit quality content on a regular basis and would like them to submit as much as they want..

This is pretty tricky what you want. IF they submit quality content then they should have more votes. Remember you can adjust minimum required votes for reaching next level of authorization and more variables in your Pligg configuration.

Your idea is not bad at all. if there is more users I will do that.

[patsol33]

Excellent mod, MUCH appreciated.

Had a quick question... on a test (using all default settings) I had a new user submit a story and voted it to 2 (avg of 2, up to level 1). On the same day, the same user then entered step 2 of a new submission and after clicking the button to step 3, was shown the "Submit limit exceeded!" message and not allowed to submit. It appears the script is averaging the second, non-submitted story from step 2 to 3 and killing the submission.

To avoid this, is there a way to disregard discarded stories (which stories are before step 3 is completed) from the average equation?

[AnAlienHolakres3]

Originally Posted by patsol33

Excellent mod, MUCH appreciated.

Had a quick question... on a test (using all default settings) I had a new user submit a story and voted it to 2 (avg of 2, up to level 1). On the same day, the same user then entered step 2 of a new submission and after clicking the button to step 3, was shown the "Submit limit exceeded!" message and not allowed to submit. It appears the script is averaging the second, non-submitted story from step 2 to 3 and killing the submission.

To avoid this, is there a way to disregard discarded stories (which stories are before step 3 is completed) from the average equation?

This is strange. As you can see in submit_antispam_main.php, discarted stories are already not taking into consideration when the equation is calculated...did u install the last version?

[wnw]

This is cool....

would help for sure.....

[thefandango]

Could you explain this setting please. It says expecting true/false but the default entry is 1 ?

description: Define if comment submission restriction policy is enabled or not
value: 1
default value: True
expected values: True/False

[chuckroast]

Originally Posted by thefandango

Could you explain this setting please. It says expecting true/false but the default entry is 1 ?

description: Define if comment submission restriction policy is enabled or not
value: 1
default value: True
expected values: True/False

Yeah that needs to be changed. It should state that 0 = false and 1=true The setting is for turning on and off limiting the amount of comments made by people in a 24 hour period.