In trac 0.12, a project can have multiple repositories. It seems like the changeset:<number> links only go to the main repo though, so if you have two repos configured, you'll only get changeset links working with one of them. So far I've seen two places where this is a problem: if you browse to .../changeset/<number>, it selects the default repository for you, and gives an error if the changeset isn't in that repository. The second place is on the wiki/tickets; a changeset link isn't clickable if the changeset isn't in the primary repository. I think the first problem could be fixed by having the base changeset request handler iterate through configured repos until it sees one where the desired changeset is present. I assume that is done somewhere in versioncontrol/web_ui/changeset.py, but I'm not having much luck actually finding the code that would need to be changed. Assuming that bit can be changed, would the second part (the dead links being replaced by no link at all) just resolve itself?
I'll be hunting around in the changeset.py code for where the default repo is chosen, but if anybody has any better pointers, I'd love to hear them. Thanks! -- 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.
