spam 5.x-3.0-alpha3
| Download | Size | md5 hash |
|---|---|---|
| spam-5.x-3.0-alpha3.tar.gz | 33.93 KB | 350d688842cd5ffa3e5171a78113a048 |
New features in alpha3:
- spam content overview page with filtering and bulk actions
- administrative pages for viewing spam module logs
- administrative pages for viewing blocked IP addresses
- log tracing, groups all spam module logs generated by one page load together
Be sure to run update.php if upgrading from earlier alpha release.
About the 3.0 rewrite of the spam module:
This is a complete rewrite of the spam module.
The spam module includes four spam filter plug-ins:
- duplicate filter: track if the same piece of content is posted multiple times
- bayesian filter: auto-learn whether or not content is spam
- URL filter: utilizes bayesian filter to auto-learn whether certain URLs are spam URLs
- node_age filter: a tunable filter that assumes the older a node is, the more likely a comment posted to it is spam
Each filter can be assigned a weight. For example, if the duplicate module is more effective, you can weight it's score 250%. If the node_age filter is less accurate, you can only weight it's score 50%. Filter types automatically set their suggested defaults.
Implementing new filters is simple thanks to the (currently undocumented) spamapi.
The spam module also Includes three content-type plug-ins:
- comment: filters comments before they hit the database, as well as when they are inserted/updated
- node: filters nodes before they hit the database, as well as when they are inserted/updated
- user: filters users when they are inserted/updated
Implementing support for new content-types is easily thanks to the (currently undocumented) spamapi.
The spam module also provides a partially-implemented interface for reporting when content has been inappropriately marked as spam.
Note: This is an Alpha release. It is not considered stable. It likely contain bugs, and is not recommended to be run on production websites. Furthermore, there is no guaranteed simple upgrade path from one Alpha release to the next, instead requiring you to drop your database and reinstall. When the module is considered reasonably stable, it will enter Beta status.