On 07/12/2007, Christian Boos <[EMAIL PROTECTED]> wrote: > > > > Well, I don't think separating that log information is really worth the > increased complexity. > But I think that adding the user info in the matched section and more > importantly, uncommenting it by default, can help. After all, that's > really needed if you want to debug the authz_policy.
Attached is my updated authz_policy.py file - with the highly complex change of removing the comment and adding the user name to the log call. ;) > - as usual, the (exact) version of Trac and the plugins used > > > > > > With the code that I'm storing in subversion I use svn:keywords to add a > > code comment to the head of the pages that include the svn values Rev, > > LastChangedDate and LastChangedBy. Would it be worth adding this kind > of > > thing to examples and plug-ins, so that its plainly visible what > revision of > > that code "users" are looking at? > > The reason I suggest this is that Trac was showing the latest revsion > number > > at the bottom of the pages and on the "About" page, but the plugin code > > isn't linked to this and somehow I was using an out of sync version of > the > > plug-in with no idea that I was doing so. > > > > I think that's a very good idea for the single file sample plugins. > I would have suggested the whole codebase, but having done that with a project here at work I know what a serious pain in the backside that is. :) Regards Stephen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
authz_policy.py
Description: Binary data
