Search options (Page 1 of 2)

I am trying out this extension on a forum running PubBB 1.4.2 with a Postgresql database. The extension installs fine, but when I click on the Antispam section in Administration, I receive this error:

On another forum, same PunBB version, but MySQL database, I don't get the error. I am guessing this extension is not compatible with Postgresql? This is with fancy stop spam version 1.3.52.

UPDATE: It seems the problem is due to this extension using the MySQL function INET_NTOA in the print_logs() function, which is not available in Postgresql. To fix I added an inet_ntoa function to postgresql by executing the following on my database:

create or replace function inet_ntoa(int) returns inet as '
select ''0.0.0.0''::inet+$1;'
language sql immutable;

To fix, in manifest.xml on line 326, change

                                </div><?

to this:

                                </div><?php

Thanks to the author for a great extension!

It's been awhile since I checked in here. KeyDog, are you still using this extension on 1.4.1? If so, I'll look into including last seen information and specifying whether the match was on IP or email. I need to upgrade my forums first (I'm still on 1.3.6). Hopefully the process isn't too painful.

dimkalinux, this extension is looking quite nice. Do you plan to add a way to enter a SFS API key and report spammers when deleting them? That would make this the perfect antispam extension in my opinion.

I didn't mean to imply that you should not use 1.4, but only that most third-party developer extensions have not been tested to work with 1.4 yet, and there were some changes to the way extensions work in 1.4, so you're kind of in uncharted territory if you do. Hence my recommendation to use the PunBB developed extension.

If you must upgrade to PunBB 1.4, then I would recommend using the PunBB Fancy Stop Spam extension. It seems that the PunBB team is encouraging people to use their in-house developed extensions, and as far as I know, they have not provided documentation for extension developers to update their extensions to support 1.4.

Well the field is called "registered" and I intended it to store the date the spammer registered or attempted to register, so that's why I use the actual registration date. But I suppose I could just rename the field to "added" so that the current timestamp will always be appropriate.

Thanks.

Ah! I misunderstood your question the first time. I thought you were suggesting that people wouldn't want to utilize the feature.

And you are totally right, I somehow forgot to add the check on that setting, so currently it is searching on email addresses whether you want it to or not.  My apologies, and I'll have it fixed in the next version, along with the other requested features.

Really? I use this setting because I want to block registrations from those using listed email addresses as well as those using listed IP addresses. Do most people only block by IP?

Or maybe the way I labeled the setting is unclear. To clarify, if you leave it unchecked, then this extension will only search the StopForumSpam database for a registrants IP address, and block the registration if there's a match. With the option turned on, it will first search on their IP address and block if there's a match, but if there's no match, it will then search on their email address, and block the registration if there's a match.

I will admit that I'm far from an expert on this subject, but doesn't it make sense  to search on both?

The way I see it, a "spam report" is just that, a report of spamming. A blocked registration cannot be qualified as spamming, regardless of whether or not their IP address or email address is listed in the StopForumSpam database. Your spamming service may have different rules as to what constitutes spam, but since my extension utilizes the StopForumSpam.com service (as indicated by the "SFS" in the name) I don't feel it appropriate to add such a feature to my extension.

That said, this is open source. You are welcome to take my extension and build upon it, and release your own StopArticleSpam extension if you wish.