The patch numcaptcha2.patch from http://trac.edgewall.org/ticket/4034 modifies only
templates/settings.html and trac/Settings.py So you can just have a copy of them to roll back the patch (or get it back from SVN). The patch is supposed to be applied to the trunk. Peronally, I'd prefer captcha to be integrated into settings than to be a plugin - it works better being a part of settings screen than any tricky filter or whatever else. Another thing - I don't feel happy with the idea having a bunch of plugins to be installed/reinstalled every time. Most of all, I'm afraid that plugin's support might stop any time and it won;t probably work with the next version of the trac, while the project itself will likely have long and happy life :) Now imagine what if one would likely need 15-20 plugins for typical installation :( "Battery included" - good old Python tradition. > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Allen Bierbaum > Sent: Tuesday, October 31, 2006 5:30 PM > To: [email protected] > Subject: [Trac-dev] Re: Captcha ready to use? Which one to use? > > > Alec Thomas wrote: > > On Mon, Oct 30, 2006 at 04:15:21PM -0600, Allen Bierbaum wrote: > >> Just like many others around here, several of the trac sites I run have > >> been getting hammered with spam. I know that Christopher Lenz has been > >> working on revamping the spamfilter plugin and I applaud that work. I > >> can't wait to try it out. That said, I am very interested in the > >> captcha work from this ticket. http://trac.edgewall.org/ticket/4034 > >> > >> Using a captcha seems like a great way to really lock down a site while > >> still allowing valid users to do what they need. The ticket above has > >> two different captcha implementations and they both seem interesting. > >> > >> Has anyone tried these systems? Are they the recommended way to do > this > >> for now or is there another effort that I should be aware of? Any > >> reason not to start running these on production sites? (I *really* > need > >> to get rid of the spam ASAP) > > > > I haven't tested the plugin on a production site yet. I'd like to get > > feedback before doing so, so if people could test it I would be > > appreciative. The plugin works against 0.10 for both anonymous and > > authenticated users. Authenticated users are only checked if > > spam-filter.trust_authenticated=false in trac.ini (same as SpamFilter). > > I was going to try it out yesterday but I held off because I didn't want > to patch and re-install the core trac system. It would probably work, > but I can't really risk breaking the site. > > Is there any way that this code could be implemented as a plugin instead > of a modification to the core code? In my opinion this would make it > much easier for people to test and refine without the risk of breaking > their current site. > > -Allen > > > The other solution on that ticket is a patch against current trunk, I > > believe. > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev -~----------~----~----~----~------~----~------~--~---
