Anti-Spam Options - Automated Post Reporter

This mod will automatically generate a report thread when a new user posts a reply to a thread that has been inactive for a time (necro-posting) and/or has included certain words in the content of their post (and signature if you want). This includes the case where the new user edits an existing post they have made to add such words.

In the included screenshots, you can see the options provided via the AdminCP to configure the product to suit your needs, the default message shown to new users upon editing a post to add flagged words, an example of a thread as listed in the designated report forum, and the body of the generated report.

I want to give a profound word of thanks to BirdOfPrey5 because it was the study of his XML files and the fact that he allows his code to be reused that allowed me to be able to package my products. :up:

Updated version 1.1:

• User is allowed to chose excluded usergroup(s) from list of available groups
• User is allowed to chose destination forum for generated reports from list of available forums
• User is allowed to opt out of generating reports (moderate posts only)
• Bug fixed where user editing existing post to include flagged words was shown moderation queue message even when posts were not moderated

Updated version 1.2

• Excluded usergroup selection is 2 columns to save space
• Added the option to exclude users by username
• New users may now be blocked from creating/editing signatures containing flagged words
• Customize the error message shown to such users
• Destination forum for generated reports is also a 2 column format
• if no destination forum is selected when saving the settings the first time, the forum used for user-reported posts is auto-selected
• Bug fixed with regards to the first post of a thread being put into the moderation queue and user post counts

Updated version 1.2a

• Resolved conflict with "Automatic Tagger From Message Content and Title"

Updated version 1.2.1

• Include new user's IP address in report post, with link to resolve IP
• Report which flagged word(s) were found in post content and/or signature

Updated version 2.0

• Added the option whether to exclude users by postcount
• Allow standard wildcards in flagged word definitions
• Allow product to either act globally or in select forums

Updated version 2.1

• Added the option whether to include posts/signature in report whether flagged or not.

Updated version 2.2

• Allowed domains: sites to which links are allowed.
• Quoted content (as long as it has not been altered) is exempt from being checked for flagged words.
• When a new user's post goes into moderation, they are shown a static error message, rather than vBulletin's fleeting message new users often fail to be able to read/understand.

Updated version 2.2a

• Found and fixed a syntactical error preventing selected forums setting from working correctly.

Updated version 2.3

• Will now auto-add the unresolved report thread prefix when creating the report if "Report Thread Prefix Management" is installed and active.

Updated version 2.3.5

• Data-type for destination forum fixed to positive integer.

Updated version 2.4

• Fixed broken link to post when the reported post is the first in a thread.

Updated version 2.5

• Replaced usergroup and forum selection settings with select elements.
• Added the option to decide whether to display the product's moderation queue message or to use vBulletin's default message and redirect.
• If your automated reports go to the same forum as user reported posts, then any subsequent user reports will be appended to the thread generated by this product.

Installation:

Download and extract the attached zip file, then upload the contents of the "upload" folder to your forum's root directory.

In AdminCP go to Plugins & Products -> Manage Products -> Add/Import Product.

Click on "Choose File" and browse to the product xml file that was included in the .zip file.

Click "Import"

You MUST enable the product by going to:

AdminCP -> Options -> MarkFL: Automated Post Reporter v1.1

And clicking "Yes" for "Reporting System Enabled?"

Support for this product can be found here:

• MHB - Automated Post Reporter
• TAZ - Automated Post Reporter

[Skyrider]

Argh, my bad. Was multi-tasking that I didn't even notice that the PHP files were completely different. Line 64 of functions_autotaggerfromcontentandtitle.php is:

function contains($text, $tag, $related_words) {

From this plugin:

https://vborg.vbsupport.ru/showthread.php?t=234026

Seems to be conflicting with your system.

[MarkFL]

Originally Posted by Skyrider

Argh, my bad. Was multi-tasking that I didn't even notice that the PHP files were completely different. Line 64 of functions_autotaggerfromcontentandtitle.php is:

function contains($text, $tag, $related_words) {

From this plugin:

https://vborg.vbsupport.ru/showthread.php?t=234026

Seems to be conflicting with your system.

Okay, my hack and the one you are using both declare a function of the same name. I have renamed the function in mine and this should resolve the issue.

Please download and install the current version (1.2a) and let me know if this fixes the issue on your end.

[MarkFL]

Originally Posted by Skyrider

...I do would like to make a suggestion that it shows in the report "which" flagged word triggered the report. Maybe displaying IP as well in the reported posts?

I have included these changes in the latest version 1.2.1.

[Skyrider]

Awesome, thanks! The system works perfectly now, and I love that the words are included now. I do have a suggestion though if you don't mind. I noticed that the system is using the *.php file in order to make the full report, eg, what text is being used.

Is there a way that a template & Languages & Phrases can be used instead?

So the text itself (the whole report) can be adjusted to fit the forums without changing the php file(s).

And can the Postcount Threshold also be -1? (checking every single member, regardless of the postcount).

Again, thanks for this system. It's very useful.

---

EDIT:

Maybe exclude specific sections/sub-sections would be nice as well ^_^.

[MarkFL]

Originally Posted by Skyrider

Awesome, thanks! The system works perfectly now, and I love that the words are included now. I do have a suggestion though if you don't mind. I noticed that the system is using the *.php file in order to make the full report, eg, what text is being used.

Is there a way that a template & Languages & Phrases can be used instead?

So the text itself (the whole report) can be adjusted to fit the forums without changing the php file(s).

And can the Postcount Threshold also be -1? (checking every single member, regardless of the postcount).

Again, thanks for this system. It's very useful.

---

EDIT:

Maybe exclude specific sections/sub-sections would be nice as well ^_^.

I will look into all of these points very soon. I was actually already thinking of giving the option to choose "Active Forums."

[Skyrider]

appreciate it!

Mind if I make another suggestion? :P

Is there anyway that the bad word filter can have a system that "must" include a specific word, and also report the rest of it? Hard to explain, so I'll give an example:

Suppose, you would filter "http://google.com". <- yes, this entire url.

That would report all posts/threads & signatures with "http://google.com" in it, but ignores anything beyond that if it includes a longer url, eg http://google.com/searchresulthere.

When that happens, the bad word is not being reported at all, seeing the system only sees "http://google.com" as a bad word. Anything added after the link, well.. you get the drill. What I'd personally like to see is if it is possible that when you filter a specific word or URL in this case, that anything beyond that ( http://google.com/*) <- like this *, gets reported as well.

I've seen on some plugins they are using such method, I just forgot what the plugins were/are called. I think the other systems were using Quotation Marks for this kind of job, eg as bad words.

test1,test2,test3,"http://google.com",test4,test5

So that http://google.com and anything beyond that url gets reported as well.

Hard to explain, but I think you understand.

The reason why I'm suggesting is this because we don't want the word itself to be filtered, but the url and anything that is being added inside that url. This is to prevent words being used of the url in the filter.

[MarkFL]

As it is, if you enter http://google.com as a flagged word, then if a new user has https://www.google.com/search?q=gauss&ie=utf-8&oe=utf-8 in their post, the post will be reported. Are you saying you would want the option that this not to be reported?

[Skyrider]

Odd, I'd have to try it out again then. I attempted http://google.com to be as a bad word, but when I enter a full google URL as your post, it didn't report it. Let me double check to see if this is still the case.

[MarkFL]

Okay, I see the issue...if http://google.com is entered as the flagged word, then https://www.google.com* will not be reported...what would have to be entered as the flagged word is https://www.google.com.

[Skyrider]

I think you noticed my issue now , though I might as well give an example with the URL I had in mind.

I've filtered:

http://steamrep.com/

Now, when I make new thread / post with this included:

http://steamrep.com/search?q=skyrider

The system is not reporting it, while http://steamrep.com is in the bad word list. Hence, would it be possible that that the system can detect the bad word seeing "http://steamrep.com" is already in the bad word list.