[Tracker-discuss] Need some help - how do I get my auditor to run for each submission?
skip at pobox.com
skip at pobox.com
Mon Jun 11 00:26:59 CEST 2007
mk> You used:
mk> database.file.audit('create', check_spam)
mk> database.file.audit('set', check_spam)
mk> while you probably meant:
mk> database.issue.audit('create', check_spam)
mk> database.issue.audit('set', check_spam)
mk> or maybe:
mk> database.msg.audit('create', check_spam)
mk> database.msg.audit('set', check_spam)
Thanks. Shouldn't this be clearly documented somewhere? Your mail sent me
into the depths of the design document. As far as I can tell the
distinction between different attributes of the hyperdatabase is only found
in a couple examples in the detectors directory. What's the difference
between issue and msg? Web submission vs. email? Is there one choke point
where I can execute the auditor? Where do web and email submissions
coincide? I'm unable to actually create a database interactively. The
example session in the Application Example section of design.txt clearly
doesn't work. I poked around a bit and tried creating a
back_anydbm.Database. That also failed. If Database objects are supposed
to have issue attributes I ought to be able to find "self.issue" somewhere
in the Roundup code but have not been able to. I did find "self.msg" and
"self.file", but the grep hits that turned up didn't seem to be related
directly to Database objects.
mk> Creating a file attachment and creating a new issue are two separate
mk> events, so you'll have to handle them separately. So, use
mk> "database.file.audit" to register file attachments checker and use
mk> "database.msg.audit" to register message checker.
Again, what's the difference between "msg" and "issue"? Can I read about
any of this anywhere?
I am more than happy to do what I can to make SpamBayes a viable spam
checker for Roundup, Trac, MoinMoin and other web applications, but I really
don't have the time to become a guru for any of those systems.
frustratedly-y'rs,
Skip
More information about the Tracker-discuss
mailing list