Edgewall Software

Changes between Initial Version and Version 3 of Ticket #3403


Ignore:
Timestamp:
Jul 18, 2006, 12:30:44 PM (18 years ago)
Author:
Christian Boos
Comment:

You meant InterTrac here, not InterWiki.

But yes, the InterTrac code doesn't interpret links locally, but let the remote Trac do the job, relying on the fact that usually the same names are used for the module in link resolvers and requests URLs. However, this is not always the case, as your example shows.

A better solution would be a generic /intertrac/<link> request handler that would dispatch any <link> to the appropriate local object.

The advantage of the current approach is that Trac servers of any version can be targeted by an InterTrac link (at least for simple links).

I'll do at least the dispatching part for 0.10, as not only it will solve this issue, but also the long standing one with the log: InterTrac links, covers the comment: links, etc.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3403

    • Property Status newassigned
    • Property Priority normalhigh
    • Property Keywords intertrac added; interwiki removed
    • Property Milestone0.10
    • Property Owner changed from Jonas Borgström to Christian Boos
    • Property Severity normalmajor
  • Ticket #3403 – Description

    initial v3  
     1In interwiki processing
    12{{{
    2 In interwiki processing
    33source:trunk/Makefile works as expected
    44s:source:trunk/Makefile generates an invalid URL, however