Serving 4205 extensions to the community
Categories
Directory Menu
Login or Register
Fly06 Spammer Blocker 
Version
1.0.2 (last update on Dec 20, 2009)
Rating
Compatibility
Votes
5
Favoured
13
License
GPL
Non-Commercial
Type
Views
9159
Date Added
14 January 2008
The Fly06 Spammer Blocker extension allows you to block the registration of potential spammers.
It uses the API provided by the www.stopforumspam.com website to decide whether the user is a spammer or not and stop the registration process accordingly. The plugin supports the default Joomla! as well as Community Builder and JUser registrations. Three criteria can be combined to identify a spammer : ip, username and email according to two decision process : 'all of them' (weak) or 'at least one' (strong). The plugin is easily configurable in the Joomla! backend and comes with useful additional features such admin email notification, redirection handling, user notification and more...
This extension is much more than a simple upgrade from J!1.0 to J!1.5. The plugin has been completely rewritten, some bugs have been fixed and blocked spammers can now be logged in the database. Moreover, this extension includes a component (backend) for managing logs and a module for showing the latest spammers to front-end visitors and/or users.
Currently supported languages: English and French.
What's new in v1.0.2?
- Username passed in the url is now wrapped in urlencode() to avoid problems with special characters such as blank space
What's new in v1.0.1?
- Use of onAfterRoute event (instead of onAfterInitialize) to make the plugin SEF-compliant
- Help files were updated to reflect the new site's urls (fly06.fr)
Reminder: Please note that the J!1.0 version is not supported anymore.
So far, the extension seems to work fine. I haven't had any errors and the site didn't crash. :)
However, it said in the description that it uses an API from Stop Forum Spam. I got an API from them, but can't find where to put it in the parameters of the component, module or plugin. I looked through the Joomla forum (since that is where fly06 refers you to) and didn't find any mention of it.
I am using the latest (v 1.0) release on Joomla 1.5.14.
Thanks for making my site a little bit safer to use.
If the API isn't needed any more, the description needs to be updated. If it's still needed, instructions need to be given as to where to put it. That's the only reason I gave this a "Good" rating instead of "Excellent".
Thanks again,
Flip
However, it said in the description that it uses an API from Stop Forum Spam. I got an API from them, but can't find where to put it in the parameters of the component, module or plugin. I looked through the Joomla forum (since that is where fly06 refers you to) and didn't find any mention of it.
I am using the latest (v 1.0) release on Joomla 1.5.14.
Thanks for making my site a little bit safer to use.
If the API isn't needed any more, the description needs to be updated. If it's still needed, instructions need to be given as to where to put it. That's the only reason I gave this a "Good" rating instead of "Excellent".
Thanks again,
Flip
Owner's reply
Hi Flip and thanks for your review.
You don't need to use the SFS API key with this extension.
The Fly06 Spammer Blocker extension only uses the 'Get' part of the API which does not require any key.
The 'Add' part is only needed if you want to add your own spam data in the SFS database which is NOT the purpose of the Fly06 Spammer Blocker extension...
Hope this helps ;)
-Fly06
bymikesimaska on April 25, 2009
After registering and installing the plugin both the front end and back end just displayed "Restricted Access". Had to manually remove the folder and edit jos_plugins to get my site back up! Too bad as I'm getting a lot of spammer registering and have to try to keep up manually. StopForumSpam lists every spammer email that I manually removed !! Still looking for good registration plug-in that blocks known spammers from registering.
Owner's reply
'Restricted access' just means that you're trying to access a joomla php file outside the joomla context...
Are you using joomla 1.5 instead of joomla 1.0 or have you changed the _VALID_MOS constant in your joomla 1.0 installation?