Module development and code questions

I'm considering building a module that uses Spamassassin rules to filter incoming content. Below are some of my notes on the topic. Note that this assumes that the reader is mildly familiar with how Spamassassin works:

Create a Drupal module that uses spamassassin to filter content.

Create a rule to apply to each role to determine whether filter applies.

Specify which node types/comments get filtered. Possibly have a per-node config that allows poster to turn on/off comment spam filter.

Specify a spam score above which content post gets filtered.

Options for filtering actions include message being:
1. denied
2. denied quietly (appear to be accepted)
3. queued for moderation
4. queued for moderation quietly

Spamassassin will need to be modified to only apply body tests, as all
header tests will be unapplicable. Consider the performance
options/payoffs between using spamassassin as a separate process vs.
using the spamd client/server configuration.

Rule sets will need to be customized for each community. Consider developing an interface that allows moderators to adjust scores for rules on a per-message-acceptance basis using a "This is not spam" button in addition to an "Approve" button. e.g. if a blackjack gaming community posts 25 posts all containing the word 'Casino' and the CASINO spam rule by default adds 2.8 points to the overall spam score, each message that gets accepted reduces the spam score for rule CASINO by some predetermined value (like 0.1). After moderators have accepted all 25 posts in this way, the revised spam score for rule CASINO will be 0.3 (most likely below spam threshold).

Hi all,

I have created a new module for our site, which enables users to rate nodes out of 5-stars.

It then filters nodes which score below a certain threshold (default 2 stars).

If anyone would like to check it out (ie beta test it :) ), feel free to email me: mabster at madprops dot org.

Cheers,
mabster

I'm trying to figure out where a module's admin (preference) settings are stored. I was playing around with the image module, but could figure out where it stores the values. I can't find them in the database. Does Drupal write them to the module file itself? If not where do these values get stored?

So when I develop my own module and I have some preferences that needed changing, where should I have them stored for that specific module?

thanks

So, i couldnt find anything about how to submit a module, or what INSTALL/README type files were needed (and how to write them...)

Anyone tell me how?

You can get the module here: http://83.88.179.12/emailpage.module

It has no install, just copy to the modules dir in the usuall manner and then go enable it and adjust it's settings.

Nick

Um, yeah, as I said, I don't know if this is the right place to post this, but I downloaded, installed and enabled the BBCode mod, and it doesn't work. Any ideas what I might be doing wrong?

I am trying to setup a new site about languages and linguistics. I post on this forum to get the advice of people that have more experience in Drupal.

I have choosen Drupal because it is simple, has easy to understand code, is extensible, works with Postgres (though does not use its power) and looks good. There are things I do not like in Drupal, but maybe it is becase I do not understand things well (I am playing with it only a week now, and I do not have much spare time :-( for it)

In the case of my site Drupal is not a CMS only - it is going to be an interface to a linguistic database. I did not want my site to be a bunch of freeform nodes that display in a nice CMS. It is supposed to be a database of linguistic data that displays and gets modified as easily, as any other Drupal content, but is well structured and can be exported to an XML document that can be later converted to a book (PDF or OpenOffice doc for example) and downloaded by an interested user. I decided to write a separate module for each kind of data (classification node, part of speech description, thematic vocabulary, lesson, exercise etc - I am still thinking how it is supposed to be organised), that takes care of editing and displaying its content. This modules are node modules, so Drupal takes care of many things, like for example comments, promoting to main page etc. - but I had to trade the design of the database in exchange. I decided that each "piece of data" will be kept in node's body as an XML or PHP, teaser will be standard HTML. I do not want to modify existing Drupal code (though simetimes I would like to do it :-) ) in order to be able to upgrade in the future, but I had to do some minor changes - like displaying teaser on the edit form. I miss access restrictions on the node level.