Stephen Moretti wrote: > I wonder if there is any mileage in extracting security logging, debug or > otherwise, into a separate log file from the standard logs? > I also added the username to the "matched section" debug output, to make > sure I really was logged out or logged in as the user I expected. > > Is there anything else that might be of use in the debug? >
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. > - 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. -- Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
