>
> That was http://trac.edgewall.org/changeset/6246, long time ago ;-)
> Well, at least a week before you started that thread, so I wrongly
> assumed you were already using that when you said it stopped working
> after the update.


The bizzare thing is I pulled a copy of trac from SVN when you told me I
needed to update the plugin from the sample plugins.  I'm not quite sure
what was going on there.  Perhaps there were some legacy files in my export
location - who knows.


I somehow fear that the permission policy issues are going to be  a
> bit hard to troubleshoot, we'll need to set up some guidelines about
> that, like:

I was actually writing an email with all of the exact files (rather than
copy and paste) when I did my double check of the contents of svn against
what was actually in the project environment.  This was going to match
almost exactly what you've listed here.   Great minds think alike. ;)


- provide the relevant excerpt from trac.ini: the [trac]
> permission_policies setting and the [components] section
> - the authz policy file if the AuthzPolicy is used
> - the output of trac-admin permission list if the
> DefaultPermissionProvider is used
> - the relevant excerpt of the logging output at DEBUG level


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?

- 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.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to